The compilers did not save us.https://twitter.com/slightlylate/status/1050753656805515264 …
-
-
Replying to @slightlylate
I think i asked you something similar before. But do you think SSR problems is unavoidable, or can it be done well? Was chatting with a couple devs at work who have done it before, and found it to respond really quickly.
1 reply 0 retweets 0 likes -
Replying to @agmcleod @slightlylate
In theory there's no reason it couldn't be done well. In practice, none of this stuff was built to make that an easy problem to solve. I'd bet that we'll see a new framework that does this correctly well before we get a better compiler for today's frameworks.
1 reply 0 retweets 1 like -
This is roughly my view too. Better tools exist, but they aren't being used; mostly for non-technical reasons in my experience. So teams go a long way with Framework Of The Month, find first paint is atrocious, then throw tools at the problem without addressing fundamentals.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @agmcleod
Is there a particular set of tools you like today? I’m a bit out of the loop.
1 reply 0 retweets 0 likes -
-
The core things they share: - easy code splitting - low structural costs (lightweight view layer framework) - an opinion on routing - strategies for avoiding polyfilling the world
2 replies 0 retweets 4 likes
We need a name for tools that share these traits
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.