that's true. My gut says we'll start seeing ng2 take ng1 user numbers soon though
-
-
Replying to @bradlygreen @IgorMinar and
Maybe not. I left for Vue, others for React. Ng 2 isn't relevant to me.
1 reply 1 retweet 1 like -
Replying to @TheOtherZach @bradlygreen and
This is after I spent 2 years writing and teaching Angular 1. I felt forced off Angular.
1 reply 1 retweet 2 likes -
Replying to @TheOtherZach @bradlygreen and
I think A2 is for a pretty different demographic than A1.
2 replies 0 retweets 2 likes -
Replying to @wycats @bradlygreen and
There was also 2015. NG1 was deprecated but NG2 wasn't ready. I felt forced off Angular.
2 replies 0 retweets 1 like -
Replying to @TheOtherZach @wycats and
I'm sorry you feel that way. But we haven't deprecated 1.x yet. It's still supported.
2 replies 0 retweets 0 likes -
Replying to @IgorMinar @TheOtherZach and
Angular is OSS project. I'd never let A2 happen behind the closed doors and then do a big reveal.
1 reply 0 retweets 1 like -
I like you guys, but... isn't that exactly what you did?
3 replies 0 retweets 0 likes -
...and only incomplete design doc drafts ready for community review and input.
1 reply 0 retweets 0 likes -
Angular 2 as a rewrite instead of iterating on AngularJS was not a result of community input.
3 replies 0 retweets 2 likes
I think the reaction most ppl had was to the "tombstone" talk, which seemed to come from closed doors
-
-
I learned a lot from that presentation, because it was not perceived as intended. Communication is hard.
2 replies 0 retweets 1 like -
I know. To be honest, I learned a lot too, as an outside observer. Hard to predict sometimes.
0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.