The value of frameworks is moving up the stack. Time to shed the "my component model is a special snowflake" bloat.
-
-
Replying to @slightlylate
...and no, this doesn't mean that Web Components are all-singing, all-dancing. Some fidelity with current practice *will* be lost. That's OK
1 reply 1 retweet 1 like -
Replying to @slightlylate
...and it's OK for same reason it was OK to not get 100% fidelity with everything you could w/ <table> + <img> to build rounded corners
1 reply 0 retweets 2 likes -
Replying to @slightlylate
...the difference in weight & ecosystem-wide compatibility are overwhelmingly positive. They outweigh local benefits of alternatives.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
^^^, BTW, is why it was also a good idea to push Promises into the language (despite the massive personal costs to
@domenic and myself).2 replies 0 retweets 3 likes -
Replying to @slightlylate
Global benefits are just that: hard to see from your particular patch. But they are also real and they do matter.
1 reply 2 retweets 4 likes -
Replying to @slightlylate
So, in a world where the world's most popular computers have flaky network connections and slow CPUs, anything that sheds JS is _golden_.
3 replies 8 retweets 18 likes -
Replying to @slightlylate
If your framework of choice isn't moving to Web Components for the leaf nodes, it's carrying too much weight in 2016.
3 replies 17 retweets 24 likes -
Replying to @slightlylate
and frankly, I think the world is tired of your constant moralizing and finger wagging.
1 reply 0 retweets 11 likes -
Replying to @wycats
: slow is bad for users, therefore slow is bad. Gonna keep saying that.
#sorrynotsorry2 replies 0 retweets 2 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.