There's a cottage industry of "thought leaders" trying to sell you one weird trick to fix what you broke with JS ("SSR!", "scheduler!", "compilers!", "preset-env!") but it's all failing. The only thing that works is *less script*. How? Structure + budgets.https://twitter.com/slightlylate/status/1018329021522706435 …
-
-
Facebook doesn't serve React with some glued together WebPack and Google doesn't "do" Closure the naive way. They come with gobs of infrastructure that their OSS projects don't benefit from. That's the difference between success and failure, and we aren't talking about it enough
-
This is why tools that do things like auto-per-browser-builds and default route-based-code-splitting are different IN KIND. They represent that full, supported stack that you need to succeed.
- 1 more reply
New conversation -
-
-
I think you’ve touched on a key point here Alex - these are already successful products / companies who can afford to put in place performance teams to further their success. Most people working in startups and medium sized companies are scraping by to survive year on year
-
There’s a reason most companies and teams follow the Kent Beck approach of ‘make it work, make it right, make it fast’ because having a fast product doesn’t meant anything if no one is using it
- 2 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.