News for hackers. Stuff that matters.
Re:Ditching responsive design by mariusmg on Friday February 01, 2013 @08:28AM (#5150560)
I fucking hate the term "responsive design" because in reality nothing is "responsive". A shitty fixed 980px site will still look like crap on 1080p 24'' monitor.

Calling it responsive just because the navigation menu is moved above the content when viewing it from the phone doesn't make it "responsive".

Re:Ditching responsive design by lmm on Friday February 01, 2013 @08:33AM (#5150571)
You know what's really responsive? Proportional width, aka the default.

HN is great and usable on my 27" desktop monitor or my 4" phone screen. Less design is more.

Re:Ditching responsive design by beaumartinez on Friday February 01, 2013 @08:44AM (#5150603)
If you call "having to zoom in to make the text even readable" great and usable, then yes, HN is "responsive".
Re:Ditching responsive design by papsosouid on Friday February 01, 2013 @11:11AM (#5151528)
>You know what's really responsive? Proportional width, aka the default.

Yes.

>HN is great and usable

No. HN is not the default, it uses both pixel and point dimensions, and makes unreasonable assumptions about them. If HN used ems or exs then it would be usable.

Re:Ditching responsive design by jordanmoore_ on Friday February 01, 2013 @09:43AM (#5150900)
Not if you use media queries that look for resolution and pixel density to make appropriate adjustments. It all comes down to the implementation. Your example is a generalisation sir. I can give you plenty of fine examples of responsive web design where it's more than "moving a menu". It's all in the implementation and the implementer.