111–120 of 398 posts
Earlier quoted context omitted.
And I have a problem with acres of whitespace. Here's one vote for HN to leave the line height right where it is.
How do you live with a centered fixed-width table that is wasting 15% of the browser window with nothing but hectares of white space then? Bumping the line-height to 1.5ish the font size has minimal impact to space efficiency, and add tons to readability.
For twitter you can disable JS and it will fallback to a ""degraded"" (a.k.a. Much faster & usable) experience.
Yes, but you have to click past an annoying prompt[1] every time. Does that not happen for you? [1]: https://i.postimg.cc/jjBSVmCX/Screenshot-at-2019-09-01-15-23...
That annoyance is considerably less than all the others a full-JS Twitter imposes. Including the motherlovin' account-creation nag that shows up all the motherlovin' time.
One click through at entry rather than random annoyance in the midst of reading? A net win. And an incredibly sad commentary on the state of the Web.
Earlier quoted context omitted.
The tap targets are minuscule and close to each other.
Related question: what is the easiest way to increase the tap zone of a HTML element using CSS? Aside: I have noticed Safari auto-inceases the touch zone for inputs and elements with ontouch/onclick events (I noticed because I had to fix an issue caused by this!)
I wish HN had a "search" button but it's OK to search through Google. I hope they will never change the design forever. It reminds me of the BBS which I still logs on through Cterm these days.
Also DDG !hn
If DDG is your default browser, you can run that in the navbar. Which I do all the damned time.
Earlier quoted context omitted.
No, voting doesn't work at all with JS disabled.
Yes, it does. I think you have something weird with your browser: with JS on, it does a light AJAX request, without it, it does the whole redirect thing.
These are my network requests when I vote with JS enabled.
HN is lightweight in some ways, but also quite bad in others. For example, every single time you vote on anything, the site sends back a 302 redirect and then a copy of the entire page's HTML in response. This means that every vote results in a response that's usually around 10KB gzipped. As of right now, for me, voting on any comment in this thread currently causes a 14KB response and takes about 1.3 seconds to fini…
Dude, the time to be angry is if your sentence were: "This means that every vote results in a response that's usually around 10MB gzipped." [megabytes, not kilobytes]
And:
"As of right now, for me, voting on any comment in this thread currently causes a 14MB response and takes about 130 seconds to finish."
Because that's the territory of modern web design.
If I were a modern product manager on a HN redesign I would just have these requirements:
Performance:
1. The site must load for at least 30 seconds before showing the contents of a page. NO EXCEPTIONS.
2. It should use 5-50 megabytes of data per page load.
3. Any action should take 5-20 seconds to complete.
Functionality:
4. (No new functionality requirements.)
This is based on my extensive experience as a consumer on redesigned apps.
Earlier quoted context omitted.
I had to pinch-to-zoom to upvote this comment. :-)
That's a feature IMO -- HN could even make them even smaller. It should take conscious effort to vote, and the small target size mentally reinforces this model; that it's not supposed to be the most common action. EDIT: See, clearly the vote targets simply aren't small enough !
