8
The DX shift no one noticed: Web interoperability (blog.logrocket.com)
submitted 7 months ago by to c/webdev@programming.dev
7 comments fedilink hide all child comments
 

These days, developer experience (DX) is often the strongest case for using JavaScript frameworks. The idea is simple: frameworks improve DX with abstractions and tooling that cut boilerplate and help developers move faster. The tradeoff is bloat, larger bundles, slower load times, and a hit to user experience (UX).

But does it have to work like that? Do you always have to trade UX for DX? And are frameworks really the only path to a good developer experience?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 7 months ago

Given the nature of Steam and previous executed data extraction, I'm scared installing and running niche/indie games now. Windows lacks

A unified GUI framework hasn't happened yet, not between OSes, nor really within each OS ecosystem. I'm not hopeful about leaps in native interoperability in that regard.

Web tech interoperability is so established and widely used, packaging and running those natively seems much more viable than any hope for supposed native long term efforts.

Not everything will be covered by web tech. But for many things, it's already viable, and exploring native integration of these web technologies is interesting.

  • permalink
  • fedilink
  • source
  • parent