Comment by vendiddy
1 day ago
I would attribute that more to culture.
For example https://diffs.com/ is built in React and it's basically instant.
1 day ago
I would attribute that more to culture.
For example https://diffs.com/ is built in React and it's basically instant.
Ok I stand corrected. Some have mentioned the React layer is very thin it's mostly vanilla JS!
I think my point still stands that, if MSFT cared, it would be fast. The issue is not the technology choice in this case.
For example, look at their demo here: https://diffshub.com/oven-sh/bun/pull/30412
It's way faster than GitHub and you check the network tab.
You'd be wrong, diffs is vanilla js with a react wrapper.
I would attribute it to physics.
If 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.
But this is way faster than GitHub isn't it:
https://diffshub.com/oven-sh/bun/pull/30412
Compare that to this:
https://github.com/oven-sh/bun/pull/30412/changes
I agree there are limitations bc of physics, but I don't think it explains this particular difference.
Which is also, or at least has also been a culture thing, because of the
"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.
Is 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:
https://github.com/pierrecomputer/pierre/blob/main/packages/...
... albeit using React inspired terminology like props and hydration.