Web bloat backlash: static, fast, printable
'Removing Next.js Got My Blog to 100 on Every Lighthouse Category' hit a nerve. One commenter says they use Next.js at work and hate it ('Why write each view once when you could write it twice?'). Another wrote a non-trivial CRUD app in plain HTML and unminified vanilla JavaScript and says it loads much faster than anything else they've built. The top question is which static site generator to use. 'Websites Should Be Printable' fits the same mood: infinite-scroll content is deliberately not designed to be printed, and someone notes how rudimentary printer support on Android and Chromebooks is.
The small delight projects share the instinct. 'Overgrown' shows tab age as plants. TitleArt recreates 1997 WordArt. Both are built for fun, with direct HTML-era charm.
The counterpoint: many commenters would note that Lighthouse scores don't pay the bills, and that frameworks win on team coordination, not user speed.
So what?
Speed and simplicity are now a differentiator you can claim cheaply. For content, docs and marketing pages, ask whether you need the framework at all, because your competitors' bloat is an opening.
Read these
Removing Next.js Got My Blog to 100 on Every Lighthouse Category
Websites Should Be Printable
Overgrown, when plants invade your abandoned tabs
Show HN: TitleArt – Make text like it's 1997