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
[–] 3 points 7 months ago (2 children)

Mozillas vision of phone apps was this. It's one reason PWAs were made and part of why WASM is where it is. One of the largest barriers to adoption against it is that apps allow for tight control from the dev, not just technically, but also from a legal standpoint. For that reason I would rather have PWAs myself, a lot of apps actually suck and are just full of dark patterns.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 7 months ago (1 child)

    So basically dev develop app to have more control over you which simple website simply not provides

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 7 months ago

    Correct. The degree that a native app could invade your privacy on the desktop is insane. For mobile, thanks to sandboxing it has a much smaller surface but still annoying nonetheless when an app could just be a web. Especially if all they do is just a glorified form filing app.

  • permalink
  • fedilink
  • source
  • parent