The incredible amounts of time & money I see teams spending to dig their way out of the Modern Frontend -- the Gordian Webpack, the TTFB-destroyed-by-SSR-that-was-added-"for performance" dance, the staffing needed to just measure how busted it is -- really saddens me
-
-
Replying to @slightlylate
whats your ideal alternative? if you had to roll a new frontend today, what stack would you use?
1 reply 0 retweets 3 likes -
Replying to @bcomnes
First and foremost, something that doesn't make adding JS feel cost-free. Next, something that's penny-pinching on bytes for most users. Lastly, something that plays well with incremental loading options. There are a few stacks that do a good job of this today (contd.):
2 replies 0 retweets 7 likes -
Replying to @slightlylate @bcomnes
Good options today include: - Open WC scaffold + Lit: https://open-wc.org/init/ - Preact CLI: https://github.com/preactjs/preact-cli … - Sapper + Svelte: https://sapper.svelte.dev/ -
@eleven_ty + custom client-side + SW ala https://philipwalton.com/articles/smaller-html-payloads-with-service-workers/ …3 replies 8 retweets 42 likes -
One danger of some of these tools is that they still make it easier than not to pull things in via NPM. That's a smell, but hopefully tools like Lighthouse CI and reasonable performance budgets can help:https://web.dev/fast/#set-performance-budgets …
2 replies 0 retweets 3 likes -
Replying to @slightlylate @eleven_ty
bundling and/or transpiling is where all the bloat entered and hides because deps, bundles and transforms are opaque. now that esm support is 'here', it seems like a bundle-less dev flow would provide to a transparent network waterfall to make dependency size less hidden
3 replies 0 retweets 6 likes
I'm super optimistic about @pikapkg and https://www.snowpack.dev/ for this sort of thing. Getting back to "no big toolchains" has tons of benefits all the way down.
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.