Skip to content
This repository has been archived by the owner on Sep 15, 2024. It is now read-only.

Future?? (Idea about AngularJS 2) #17

Open
chandu0101 opened this issue Oct 28, 2014 · 8 comments
Open

Future?? (Idea about AngularJS 2) #17

chandu0101 opened this issue Oct 28, 2014 · 8 comments

Comments

@chandu0101
Copy link

I just saw angularjs 2 presentation https://www.youtube.com/watch?v=gNmWybAyBHI

summary :
controllers,DDO(directive def obj),module = RIP , now they are building everything on components/DI etc.

Instead of mimc'ing angularjs 1.3 features , how about embarrassing new features ... ? if you have plans to do this i'm ready to help , i only have 40 days scala exp ,but i have plenty of time and interest.

Thank You
Chandra

@mysticfall
Copy link
Member

Thanks for the suggestion! I didn't realized that AngularJS 2 has sufficiently shaped up to provide enough substance to work on. In that case, I'd indeed be interested in study and build upon the framework as you suggested.

I'm just not sure how soon, or how dedicated I'll be able to work on this issue, so your contribution would be much appreciated if you could help.

@mysticfall mysticfall changed the title future? Future?? (Ideas about AngularJS 2) Oct 29, 2014
@mysticfall mysticfall changed the title Future?? (Ideas about AngularJS 2) Future?? (Idea about AngularJS 2) Oct 29, 2014
@chandu0101
Copy link
Author

sorry dude i can't help , the journey i started with this aim took so many turns and ended up here http://chandu0101.github.io/sjrc/
https://github.com/chandu0101/scalajs-react-components
now in love with reactjs .
btw good luck with your project.

@mdedetrich
Copy link

Just wanted to make a general comment here about AngularJS 2.

I wouldn't worry too much about supporting or even taking into account AngularJS 2. Its changing/moving very rapidly, and its design is incredibly different to AngularJS 1. Angular JS 2 is trying to leverage more of the JS ecosystem rather than overbuilding its own (i.e. using EMCA script modules over Angularjs 1.x modules) and its also pushing more and more code into Web Components

I think at this point its just too much work to deal with it, and we may hit blockers in regards to things like modules

@mysticfall
Copy link
Member

I agree with @mdedetrich about not hurrying up to catch up with Angular 2 yet.

Personally, I'm more interested in testing the web components for now and planning to start work on it soon, but not necessarily in the context of Angular 2.0 though.

But as it seems to move toward that direction also, I suppose it might help us migrating to Angular 2.0 later also.

@briantopping
Copy link

How are you guys still feeling about this position a couple of months later? I don't have the experience with Angular to say "it's stable", but I like developing with it so far. The icing on the cake would be to avoid learning typescript idioms and possibly contribute back to ng2 bindings in the process.

@mysticfall
Copy link
Member

Honestly, I've been too occupied with my current project (which still uses Angular 1.4) recently to spend much time in considering the migration path.

So I'm afraid I don't have anything specific to share with you on this subject yet. But considering the pace with which Angular seems to move towards 2.x, I have little doubt we'll be revisiting this soon.

Sorry I couldn't say anything more than this for now.

@briantopping
Copy link

briantopping commented Oct 4, 2015 via email

@breatheeasy86
Copy link

When I was referred to this blog by one of my batch-mates who used to participate along with me at Angularjs Training In Hyderabad center who is also a genius in the subject helped me learn more the tough subject in easy. Thanks you for the information which is to the point, reliable on this website.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants