31–40 of 51 posts
On my machines (desktop and smartphone), this implementation is noticeably faster than the real thing; or at least that's how I perceive it. I never worked with, or even tried, React and such libraries but a bit surprised. The code in this version here must be much more complexe, and the server much smaller, yet (feels as if) it is faster. Am I the only one experiencing this and surprised by it?
Earlier quoted context omitted.
Remix (which uses React as the UI library) is server side rendered
True, but it still needs to download a big chunk of JS to have client-side routing.
Huh, how cool. This may just be an odd coincidence but I have very photosensitive eyes so there are a few custom settings I cycle through whenever I need to reduce eye strain. Switched my settings back to mfg preset and for some reason the website is easier on my eyes than regular HN. The colors are all the same, the layout is the same, the zoom is the same - can't really figure out why but I thought that was neat.
Very great work! I love destroying the notion that you have to use some esoteric hyper-optimized tech to get quality performance.
On my machines (desktop and smartphone), this implementation is noticeably faster than the real thing; or at least that's how I perceive it. I never worked with, or even tried, React and such libraries but a bit surprised. The code in this version here must be much more complexe, and the server much smaller, yet (feels as if) it is faster. Am I the only one experiencing this and surprised by it?
JS apps like this should be faster, since they are downloading the "shell" of the application once and simply rendering content from lightweight JSON data requests rather than requesting an entire HTML page and re-rendering it. (Which also requires the server to query and send back things the client already has, like your username and karma) Single page apps get a lot of hate here because they tend to end up as huge…
Edit: It does in-fact load a JSON payload along with client-side routing as well if you click to view comments. But then if you use browser refresh, it renders as a traditional server-side request. So true to its name, Remix is a blend of both approaches, playing on the strengths of each.
Earlier quoted context omitted.
True, but it still needs to download a big chunk of JS to have client-side routing.
Yes, though I wouldn't call it a 'big chunk'. The whole page was 500KB and it seems the Remix library code is a small piece of that (measuring in the 10s of KB).
Only thing I notice is that the collapse button isn't a button and is the entire [-] thing, vs. just the - or + being an actual button. Very great work! I love destroying the notion that you have to use some esoteric hyper-optimized tech to get quality performance.
I don't know the stats, but I could imagine that HN is used by quite some mobile users, so an UX update would be appreciated.