I would attribute that more to culture.
replyFor example https://diffs.com/ is built in React and it's basically instant.
I would attribute it to physics.
replyIf the entire page is rendered on the server, the information required to do so is presumably reasonably approximate (same datacenter). If most of the page is rendered on the client, the information needs to be pulled in from arbitrary physical distances.
At some point the engineering really is this simple.
Which is also, or at least has also been a culture thing, because of the
reply"Oh no, we can't possibly do the computation of all that on our backend! Yikes! Let that run on every single client instead! Let users spend their own compute over and over."
culture.
You'd be wrong, diffs is vanilla js with a react wrapper.
replyIs it? I looked at the source but it doesn't appear to be react. It has a React API but also a "vanilla js" API and when I looked at the code it seems to be doing everything by hand:
replyhttps://github.com/pierrecomputer/pierre/blob/main/packages/...
... albeit using React inspired terminology like props and hydration.
Dropping Javascript and going back to native yea
replyI don't think UI frameworks will go away any time soon. They solve a very different problem from React Native.
replyit was also terrible, but in a different way
reply[dead]
reply