Comment by sitharus

9 months ago

I don’t understand how that’s at odds with having spec-valid HTML and CSS

Because updating to become conformant might come with the risk of making it a "modern" overhaul :/

  • You don't need

    > no cookie popups, no "subscribe to our newsletter" slide-ins, no phenomenon where the content loads but then a second later the page resets and re-loads the content again (probably with more ads or something)

    to fix rendering layout using tables and cell width to render comment levels.

    Just a few lines of CSS and Arc really. That would be a big overhaul only because HN is very small, but not that big in absolute.

    • And I just want a reasonable font size. On desktop it is miserable -- I always need to zoom to 133% to match the font size I see on other websites. On mobile it is ok.

      3 replies →

  • So, I'm fearful of that as most people here, but if any entity can manage a respectful update, it has to be someone Y Combinator can pay.

Because HN's development prioritized "good for the user" over "good for browser developers". https://www.w3.org/TR/design-principles/#priority-of-constit... https://datatracker.ietf.org/doc/html/rfc8890

Anyway, the "errors" that OP mentions are simply just deprecated attribute styling and like, one or two instances of center tags. Hardly breaking anybody's back to continue supporting those.

  • Apparently not “good for the user”, given how many people here have commented about the increased font size or custom CSS extensions they need to use on HN to make it readable.