tl;DR: in 2016 we still can't render "subdocuments" to which only a subset of CSS applies. Will change
-
-
I'm honestly interested most in functionality. We want to enable devs to create great UX *easily*.
2 replies 0 retweets 1 like -
I'm interested in teams being able to style things without breaking each other's stuff.
1 reply 0 retweets 4 likes -
Replying to @rauchg @traviskaufman and
you can make it easy, but "easy and breaks tomorrow" doesn't quite fit the bill
1 reply 0 retweets 1 like -
we can make this work without moving the entire ecosystem to JS.
2 replies 0 retweets 1 like -
*today* it's not possible however. https://github.com/w3c/webcomponents/issues/71 …
1 reply 0 retweets 2 likes -
Replying to @rauchg @traviskaufman and
it can be done via compilation, and before you tell me I'm being silly, think about 1/
1 reply 0 retweets 0 likes -
how much effort has gone into JSX and CSS-in-JS 2/2
1 reply 0 retweets 1 like -
Replying to @wycats @traviskaufman and
we tried the compilation approach, it was much slower and error prone than CSS-in-JS
1 reply 0 retweets 1 like -
I see CSS-in-JS as a great bridge until we get the features we need in the specs and engines
3 replies 0 retweets 2 likes
a bridge to nowhere require a complete rewrite.
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.