6 ms·
Will Wikipedia ever get responsive? [EDIT:] In other words, Wikipedia seems to be the last vestige of the dumb old "separate web for mobile" mindset of ideas l
by jessaustin 10y ago
Will Wikipedia ever get responsive?
[EDIT:] In other words, Wikipedia seems to be the last vestige of the dumb old "separate web for mobile" mindset of ideas like WML. Media queries are just better, and would prevent this inane "that link sucks for half of us; here's one that sucks for the other half" crap.
- feld 10y agoWhat does this mean? edit: oh dear, responsive web design.
- drostie 10y agoResponsive design is the design ideal of not having two separate sites -- one for mobile and the other for desktop -- but rather just being able to visit one site and have its CSS dynamically adjust so that it looks good in all screen sizes.
- feld 10y agoIf you can do it without adding a bloated JavaScript framework and adding tons of requests to a page load, sure. If you can't do that I'd prefer auto detection by the load balancer and redirects to the mobile site
- extrapickles 10y agoYou can do a fair amount these days with CSS thanks to flex-box, it handles the row based layout transition to column based quite well. A benefit of using CSS is that it handles browser zoom and high dpi screens much better as you can use units other than pixels (eg: em/rem, vh/vw, %). From a architecture point of view, you want to keep layout logic out of the JavaScript anyways as JS should be for interactions and other 'nice to have' behaviors.
- RobertKerans 10y agoJesus, you don't need frameworks or sniffing, it's an almost all-text site with very minimal styling. It's almost more difficult to make it non-responsive. There isn't anything really on the desktop version that isn't on the mobile, so I'm not sure where those extra requests would be coming from. Sorry for the the tetchy reply, I just find it nuts that, to get around writing maybe a page of CSS, people build and maintain an entirely separate site that has to be in lockstep to the the first, along with ever-reliable sniffing, and then say that is the simpler way to do it. There are several scenarios where it turns.out to be useful; this isn't one of them
- nxzero 10y agoWikipedia is responsive, so not clear what the comment meant. Info on what response design is on Wikipedia: https://en.m.wikipedia.org/wiki/Responsive_web_design https://en.m.wikipedia.org/wiki/Responsive_web_design
- jessaustin 10y agoHaha that's an ironic URL. Clearly I was wrong about Wikipedia's use of media queries, but that makes the persistence of the ".m." subdomain even stranger. It's time to start 301'ing this.
- RobertKerans 10y agoThe responsive bit doesn't really work though. The mobile version does, but there doesn't seem to be any good reason for that being extra functionality, rather than it just being how the site should reflow at smaller sizes
- deleted 10y ago[deleted]
- unethical_ban 10y agoAs someone else said, "responsive" sometimes means loading both versions of a site and being readable for both desktop and mobile. If Wiki Desktop has a lot of features or content that shouldn't get loaded on mobile, it's a bit trickier to do that. Although I agree, at least some kind of media detect/redirect may be in order.
- jobigoud 10y agoI don't undertand why the mobile version doesn't have a link to the talk page. For some articles it's a very useful additional reading to the main page.
- CamperBob2 10y agoIf Wiki Desktop has a lot of features or content that shouldn't get loaded on mobile... Except it doesn't. The whole idea behind the iPhone's browser was to avoid the need for crappy "mobile" versions of web sites. It's a crying shame that this vision had to fail because a bunch of underemployed web developers were obsessed with fixing things that were no longer broken.
- _RPM 10y agoThe reason for a separate mobile site is that we can transfer less data over the wire. mobile sites typically aren't as feature filled as the desktop sites.
- ethbro 10y agoWhat features does wikipedia have besides collapsing sections?
- ant6n 10y agoBandwidth isn't the issue as much as latency. Those collapsible sections where the content isn't loaded just mean I have to wait 10 times for 20s while trying to read an article, rather than once for 25s upfront.
- spullara 10y agoLatency is almost always the killer on mobile (hell, on desktop too) rather than bandwidth for web pages.
- jacalata 10y agoWikipedia has a large audience in areas where bandwidth is very much an issue.
- robocat 10y agoLooking at a probably large page (Intel), html content for everything before references is about 250k, which becomes say 50k compressed. Maybe for first world connections, that could be speculatively preloaded. IP address to lookup country is enough to guess?
- coin 10y agoWhich is why we have to play games like forging the user agent to get the full desktop site
- revelation 10y agoIf only we had ever invented a way for users (agents) to signal their preferences to remote servers. What's that, cookies exist? Someone tell people, it seems everyone believes those are just for invading user privacy. (Wikipedia included)
- notatoad 10y agowikipedia has a big "never change anything" culture that resists any design changes to the main site, but doesn't seem to care about the mobile site. more likely we'll see m.wikipedia.org become more desktop-friendly and responsive before we see it happen to "desktop wikipedia". (and really, the m.wikipedia site is quite nice to use on the 11" screen i'm reading on now)
- jimktrains2 10y ago> wikipedia has a big "never change anything" culture that resists any design changes to the main site, but doesn't seem to care about the mobile site. Except for the deletionists. They like to change things!
- deleted 10y ago[deleted]
- rosstex 10y agoTry this: https://www.wikiwand.com/en/Eastern_Air_Lines_Flight_980 https://www.wikiwand.com/en/Eastern_Air_Lines_Flight_980
- Kronopath 10y agoI'm sorry, what? Last vestige? That's not even close to being correct. Off the top of my head, here are some websites that still have a separate mobile domain: YouTube, Facebook, Reddit, Twitter, and a whole host of smaller websites as well. Granted, many of these do some kind of automatic redirect, so that you're redirected to the appropriate domain for the device you're using regardless of the link you follow. But none of them do the kind of responsive-design-and-media-query approach that you're talking about to differentiate between desktop and mobile.
- dang 10y agoWe detached this subthread from https://news.ycombinator.com/item?id=11836580 https://news.ycombinator.com/item?id=11836580 and marked it off-topic.
- LoSboccacc 10y agoMedia query are at most marginally better. They still suck for all devices with high resolution and low size or large size but low resolution.
- tamana 10y agoIs that a flaw in media queries, or we devs writing bad queries?
- LoSboccacc 10y agoFlaw in media query. They work on resolution and on pixel density as reported by the device but you have no way to know if it's a small size high density screen or a large screen with average density. There are 13" laptops with a resolution which overlaps with the higher end mobile phones and that is where mq falls apart because you can't tell where you are. The real issue is with all browser reporting the same fixed dpi, for reason which make sense in context but don't allow to discern all cases. We work with a mix of media query + user agent sniffing to enable mobile queries only on mobile stuff. It was all fine and dandy as long as pc had >1280 pixels, tablets where between 768 and 1024 and phones below that range. Now that everything overlaps with everything, not so much, and because all browser reports metric around the 96dpi magic number, there's no solution. At least making a media query in em instead of pixel saves you from the trouble with people zooming on pages. And if your website is responsive and allows iframing, it's even worse.
- PhasmaFelis 10y ago> all browser reports metric around the 96dpi magic number Why do they do that?
- gsnedders 10y ago> The real issue is with all browser reporting the same fixed dpi, for reason which make sense in context but don't allow to discern all cases. I'm certainly unaware of browsers doing this, except for a few old ones on desktop and Windows Phone 8's IE, and I can't find anything claiming other browsers do this. Certainly it's never been an issue I've hit.
- Washuu 10y agoUnless they get rid of the vast amounts of position: absolute; in the Vector skin it is unlikely. Which will most likely require switching out entirely to a new skin. Unfortunately many extensions that are not parser extensions rely on the Vector skin to function.