It's worthwhile to ask questions like this from time to time, and it's one of the values "new blood" brings to any community (asking the same questions but a ye

It's worthwhile to ask questions like this from time to time, and it's one of the values "new blood" brings to any community (asking the same questions but a year or so later since the last person). In this case, OP, you've "mixed metaphors" so to speak - your title is about tables, but then you mix in inline-styles and non-responsive which open the possibilities of the answers quite a bit. I think your question can be broken into two parts: (1) the design of HN, and (2) the tech parts. 1) Over the years, people have posted many suggested HN redesigns. Inevitably, they've made much more whitespace - making it more like {reddit | digg | etc} - and people always are polarizing in their comments ("Hate it - how can I function with this many scrolls?!?!" or "Love it - HN looks like crap currently!"). I suspect the "Love the current design" crowd is/has been in the majority or perhaps pg himself is in that group - either way, I've yet to see a redesign post that a large group of the community embraced. The end result: the majority of people seem like the way it is now so nothing has changed. 2) For the tech aspect, I have to ask whether you see "HTML-tables, inline-styling" as perhaps the reasons behind the "non-responsive"? Do you propose that moving to a CSS-based grid system with external stylesheets would make the system so much more responsive that we wouldn't have trouble? That's not necessarily the correlation you've drawn in the OP but it is possible that you think these are the reasons, I suppose (or contributing factors). pg/admins have talked about the server before (and it's recently been upgraded/replaced). They've also talked about the DDOS attacks they have been under as well (I think they are on Cloudflare now to help mitigate this). In the end, it's a single server managing a large community. Inevitably there will be problems when you mix those two.