When's the last time a JS library was called a defacto standard and it was still the overwhelmingly dominant solution 3 years later?
-
-
Replying to @wycats
The positive spin on this would be that the JS ecosystem is very churny - lacks stability at times. That may be part of what drives that.
1 reply 0 retweets 1 like -
Replying to @AdamRackis
There are solutions (like Ember) that prioritize stability (helped by the stability promises of JS itself) but we don't need JSR321: Web Fwk
1 reply 0 retweets 3 likes -
Replying to @wycats
True - though I think React hits a bit of a better sweet spot there - a *little* more churn for a more rapid improvement.
1 reply 0 retweets 1 like
Replying to @AdamRackis
React is fine, but vdom is not the end of the story. "it's a defacto standard" is just a way to discourage alternative approaches
8:07 AM - 17 Oct 2017
0 replies
0 retweets
8 likes
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.