DEV Community

Discussion on: Stop Using React

Collapse
 
qm3ster profile image
Info Comment hidden by post author - thread only visible in this permalink
Mihail Malo

Numbers correspond to those in the article:

  1. - Code splitting
    • Faster frameworks like solid
    • Static/SSR+cache homepage, so that the webapp is preloaded while you complete login authentication flow
    • SSR (at edge, like Cloudflare Workers or Netlify Edge Handlers) if you really need it. (Really only worth it for minor public media and shops)
  2. - It's less expensive for a recurring user to download carefully selected json data than the same boilerplate HTML again and again.
    • Many (most?) commercial sites do benefit more from wealthier users.
  3. - Such phones need different experiences than what phablets more powerful than a 2010 PC need. Yeah, maybe some of that would be psychologically healthier, but that in itself is a disincentive for many business models. So providing a separate experience for ancient phones and other accessibility tools is simply not a benefit to them.
    • Web workers are lacking some APIs, the exact list at a given time is unclear. At least SharedArrayBuffer is coming back.
  4. The web was "made" to transport text documents with <font> and <blink> tags. The experiences that we need to provide, such as offline-first never-reloaded mobile and desktop applications, are completely at odds with that. Attempts to modernize the platform in a somewhat compatible way, such as WebComponents have failed. Best thing we can hope for at this point would be headers that completely break old stuff.
  5. - Administrative fraud by the organization and the zucc, as well as their much more sinister political involvement has no bearing on viability of software libraries (intellectual property is not property, copyright is statist peepeepoopoo) or architectures.
    • VDOM, absolutely wasted work, was necessitated by the stateful nature of the DOM, and enabled a tremendous productivity improvement. The web as a platform should be eternally grateful to it. More performant alternatives have since been created, but nothing is quite as abstract and composable. Best efforts are in the direction of compilers, such as Svelte and Elm, since they can transform the purely functional components to DOM mutations instead of running the abstraction on the millions of client machines.

All in all, let's hope we get direct access to DOM from WASM before everyone is so fed up that all HTML permanently gets replaced by <canvas> with WebGL.
Which is when accessibility will truly be gone for good.

Some comments have been hidden by the post's author - find out more