#UseThePlatform doesn't mean "no" to JS, but "yes" to powerful HTML and CSS features. Don't build for JavaScript, build for the Web!
-
-
Honestly, I don't think we all are on the same side. Many want to own their own meta-platform, and don't really care about the web.
-
Ember is pretty good here, so I'm always happy to have these conversations, but others explicitly want the web to only be JS+gfx+net
-
with what Others are you shadow boxing? Just curious. I know of GPU UX toolkits under way, and JS+WebGL games, but...
-
I've had React explicitly devs tell me here they just want JS + graphics, no DOM or CSS
@wycats -
They're not building for the web platform, they're building a web runtime for the React platform
@wycats -
and unfortunately this mindset has infected many others
@wycats -
yep. And they win because their opposition is divided in message.
-
"the we is so fragmented, Learn Once, Write Anywhere sounds awesome"
- 1 more reply
New conversation -
-
-
I think the key is setting the bar and then frameworks cam compete on dx etc
-
works for me. An actual target to hit sounds awesome.
#TooMuchJS is not a performance metric. -
But it's not untrue either. We shouldn't shy away from advice because it's not a specific #
-
it's actually wrong. It doesn't have anything to do with timing at all.
-
"too much synchronous JS all at once before interactivity" is real.
-
but if you say that people will notice that there's something to do other than delete your framework.
End of conversation
New conversation -
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.