When I helped start the Web Components effort, a goal was to end framework wars at the component level. About time:https://twitter.com/domenic/status/769344873027829760 …
-
-
Replying to @slightlylate
what about rendering in Node? The article doesn't mention that, and so far I've only seen jsdom / browser solutions - not good
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
: rendering in node is fine I guess...it just breaks down when you then decorate with 100's of K of JS at runtime
1 reply 0 retweets 1 like -
Replying to @slightlylate
: that causes the lock-up ("uncanny valley") I'm talking about. If the stuff you render isn't interactive, it doesn't count.
3 replies 0 retweets 0 likes -
Replying to @slightlylate
: what's mind-blowing about PRPL is how fast Polymer gets *interactive* UI on-screen.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @yoshuawuyts
Jason Miller 🦊 ⚛ Retweeted Jason Miller 🦊 ⚛
Would like to see that generalized. Web Components should help all frameworks interop:https://twitter.com/_developit/status/769229701181235200 …
Jason Miller 🦊 ⚛ added,
2 replies 0 retweets 0 likes
yeah so that's something I'm not buying - too much spec to parse - but watching this talk, it's been 12 months @slightlylate
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.
Oh by the way...
you can use Preact to build tiny VDOM-powered Web Components now