I would kill for a web renaissance to return to this format of webpages, as least as an option. Not only loading improves, but also navigation and accessibility.
Indeed. That's why, when they finally kill old.reddit, I may legitimately stop using it entirely. They've already banned most of the good apps, forcing the pretty terrible official one.
Recently the old reddit szopped working for me even after going to account settings and opting out of new design again (it was already marked as being opt out) across all my devices. Even after manually navigating to old.reddit.com, clicking any link would take me to new again. I had to install special extensions to reroute to old reddit everywhere.
It's very frustrating whenever this topic comes up that people see no middle ground between "the website as it is right now" and "some bloated JavaScript monstrosity". There is lots of room for improvement that would not turn it into "a bloated JavaScript monstrosity". How about bigger touch targets? Half the time when I go to vote on a comment on mobile I vote in the wrong direction and have to undo it. Same goes for using the search feature: I constantly fat-finger the drop-down search options on mobile.
Even though I usually prefer mobile websites to apps, most of the time for HN I browse using Octal instead of the website because the website is such a pain. And it wouldn't take very much to make it better, which makes it so annoying that people have knee-jerk anger to the prospect every time the subject comes up.
And lose even more precious space for reading? No thanks. Zoom in before you vote if it's a problem for you. You might say "how about drag up/down?" but then you can't scroll reliably on the page.
There's all this blank space to the left of the comment. Some of that could be used for bigger arrows.
Or some of the buttons on a comment could be hidden until you tap the comment. (And you can do it in CSS if div toggle is an offensive amount of javascript.)
There are some low-hanging fruit that would make the experience better. It's fine but it's not great.
The Octal app has better touch targets on mobile and manages to show more text at the same time. Here’s a pair of screenshots from my iPhone of the top of the “Is Rust Faster than C” comments. [0] is mobile Safari, [1] is Octal. The app shows more text.
This is exactly what makes me nuts about this whole debate: the complete lack of empiricism or nuance. People would rather just have their knee-jerk outrage about JavaScript or web design fads, instead of actually checking whether the things they’re saying are true.
The font is bigger in your first example, the text uses twice the space (or your screenshots are different resolutions?). I greatly prefer it because it's easier to read. You could zoom out if you want, I guess.
But you could move the arrows to be to the right of the [-] and space them out a bit, sure, so they're easier to touch.
Anything that would introduce any amount of unneeded Javascript would make HN worse. It's the cancer of the modern Web. The current design shows that it isn't needed at all.
So is Manifest v2 ad blocking and plenty of people are screaming about killing that one.
For a proper HN technical-solutions-only response, have the rewrite functionality reside in a WASM module cached locally and run in the browser, with a transparency ledger proving everyone sees the same WASM modules. This way any MitM attempts by the service are reproducible and undeniable.
v2 is not a MitM concern (but it is a malicious code concern). Before quibbling about this consider that if v2 qualifies as a MitM concern then pretty much every other piece of software also does. That isn't in keeping with the spirit of the term.
The outrage is threefold, because there is no viable alternative, because it infantilizes users, trampling their agency, and because it clearly serves corporate interests at the expense of the user.
As to your proposed solution - the rewriting needs to happen on a separate device in order to avoid pushing extra data across the network. If you're already self hosting that service then there's no need for a transparency ledger.
One more realistic option could
be to have an "LLM browsing proxy" where you chat with an LLM via text, and it does the browsing and parsing and extracting, with links etc.
