> Although taking Google on head-first would be foolishness worthy of Don Quixote, there are ways that we can change things for the better. One is to demand tha

> Although taking Google on head-first would be foolishness worthy of Don Quixote, there are ways that we can change things for the better. One is to demand that websites we use and/or maintain follow either the Progressive Enhancement or Graceful Degradation design philosophy. The latter item is something that is integral with HTML and CSS designs, with the absence of, or error in any of the CSS files merely leading to the HTML document being displayed without formatting, yet with the text and images visible and any URLs usable. Hopefully the strategy laid out in this article is adopted more and more. Frameworks such as SvelteKit [0][1] and NextJS [2] already allow developers that were used to develop bloated SPAs to create progressively-enhanced websites that work without client-side JavaScript. Also, the landscape of frameworks that don't really require client side JavaScript is getting pretty good with HTMX [3], Rails and co adopting HTML Over The Wire [4][5]. Unfortunately, the market incentives simply aren't there, there's not a lot of money in developing websites (or web apps) that work without client-side JavaScript and bloated browser APIs, so we're left to see if simply improving the tooling will be enough for developers to create less bloated websites (whether that's intention or not). [0]: https://kit.svelte.dev/docs/form-actions https://kit.svelte.dev/docs/form-actions [1]: https://kit.svelte.dev/docs/glossary#hydration https://kit.svelte.dev/docs/glossary#hydration [2]: https://nextjs.org/docs/guides/building-forms#part-5-form-submission-without-javascript https://nextjs.org/docs/guides/building-forms#part-5-form-su... [3]: https://htmx.org/ https://htmx.org/ [4]: https://hotwired.dev/ https://hotwired.dev/ [5]: https://turbo.hotwired.dev/ https://turbo.hotwired.dev/