shipped syntactic changes that were mutually exclusive with Py2.x. This made it impossible for Django to use the shim approach we 10/
-
-
Replying to @wycats
used in Rails, and which got us on the "latest Ruby" train literally as early as was plausible. If you want to disagree with this 11/
1 reply 2 retweets 4 likes -
Replying to @wycats
analysis, you need to find an explanation for the wide difference in OUTCOMES between Py3 and Ruby1.9. Again, encodings ain't it. 12/12
8 replies 0 retweets 7 likes -
Replying to @wycats
Do you think
@angularjs will face similar challenges with their big leap to 2.0?3 replies 0 retweets 3 likes -
Replying to @gdpelican @wycats
So many people sitting on Angular 1 apps going "Wow, an upgrade is the same amount of work as changing frameworks... :-( "
2 replies 4 retweets 15 likes -
-
Replying to @wycats @gdpelican
actually A2 adoption is already at ~50% of A1 just two months after the 2.0 release. Interest in A2 is huge.
2 replies 23 retweets 31 likes -
How are you measuring adoption? Agreed interest is huge but would be surprised about that adoption metric.
1 reply 0 retweets 3 likes -
https://www.youtube.com/watch?v=3eOFCn5COvc&feature=youtu.be&t=29m40s … we believe this is the best metric we have for measuring active development right now
2 replies 0 retweets 1 like -
Replying to @IgorMinar @iammerrick and
of course in terms of LoC A1 beats A2 with a much bigger margin - it's just a matter of time though.
3 replies 0 retweets 1 like
I'll be keeping an eye on it. I'm a student of adoption and breaking changes and A2 is a great case study.
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.