Hacker News new | ask | show | jobs
by jokoon 1370 days ago
It's really funny because I asked on stack exchange why websites are slower than apps, my question for removed for being opinion based, and I got an answer about hydration.

In my view, the dom should be made obsolete, and there should be tighter restrictions, by making things immutable, or just completely redesigning how the dom works.

I'm not an expert, but the dom smells very weird.
2 comments
pjc50 1369 days ago
You cannot obsolete web browser features. That is simply not going to happen because of the long tail of devices. I'm not sure how you'd want to redesign the DOM, but you can't do that in a backwards-incompatible way either.

You could probably speed up pages significantly by introducing deferred rendering to the DOM, but: backwards incompatible change.

(That was my answer about hydration that you didn't like)

link
nescioquid 1370 days ago
The protocol and the document object model essentially assumed a static world. It's amazing what we've cobbled on top of an essentially stateless mode of encoding/structuring and accessing documents.

Why stop at the dom? Why not the protocol too?

link