5 ms·
The detail page for the first feature they mention, limiting line-width [1], makes me think: Wow, it sure takes a lot of analysis and discussion to make what is
by jrochkind1 6y ago
The detail page for the first feature they mention, limiting line-width [1], makes me think: Wow, it sure takes a lot of analysis and discussion to make what is a pretty straightforward and simple change. (Recall, too, this has been in the works for at least a year? And still isn't deployed to English wikipedia?)
Which makes me realize there's sort of an ironic situation. When a site is beginning and small, you don't worry too much about the precise details of how you've doing things, you figure it's more important to get it out there, and it can always be changed later.
Then, someday, if you're lucky, the site is huge, with lots of traffic, lots of dependencies, lots of people paying attention to it... and you are much more reluctant to make changes, taking them very seriously with lots of consideration... so now are stuck with whatever people decided years ago without much consideration at all!
[1]: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Features/Limiting_content_width https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improveme...
- notatoad 6y agoseems like the usual workaround to this paradox is to start a new "alternative" ui and allow the original site to stagnate. wikipedia did this with their mobile site - on a desktop-sized browser, it's a vastly superior reading experience to the regular wikipedia, and was implemented with virtually no controversy or fuss because anybody who was going to get angry about changes just continued to use the main desktop site.
- Falell 6y agoThis is the core of "enterprise" things. Many times clients, (especially paying business clients) care more that "things that worked yesterday should continue to work today" than about the enhancements, or even "breaking fixes", that you want to deliver for your product.
- davidivadavid 6y agoThanks for the link — that subject has been my #1 complaint with Wikipedia for a long time. I'm glad they're finally doing something about it, even though it seems like I still won't be happy with it — judging by the wikis where the update is active, it's still too wide. The rationale in the article is interesting, but IMO wrong — the idea that you need to balance scannability and line length suggests that line length is the main factor in improving scannability, when it seems obvious that what wikis have been missing for a while is better, probably sticky tables of contents for quick navigation (which something like Wikiwand figured out a while back). Making users scroll 25% less is a poor solution to improve scannability, and degrades readability tremendously. There are issues tied to the variability of layouts on Wikipedia that are more legitimate (how to deal with boxes, etc.) and would involve deeper design changes, but they would probably be worth it considering how important the basic reading experience is to wikipedia.
- jrochkind1 6y agoI just got link from the OP, but yeah!
- pferde 6y agoThis is what I don't get. Why not just make your browser window narrower? Wikipedia is one of increasingly smaller set of sites which have the decency of NOT WASTING MY FRIGGING SCREEN SPACE by putting text into a narrowest of columns in the middle of my screen and leaving the sides empty. I get that line scannability is an issue for some people, but that's why _you_ can adjust the way _you_ read the article on _your_ device, without affecting _anyone else_. Web browsers, and desktop environments in general had this magic window-resizing ability for decades. At least there are cool browser extensions like CustomCSS, which allow me to fix sites I visit often. I guess I will be adding Wikipedia there soon... :/
- davidivadavid 6y agoBecause I don't want to spend all day resizing my browser when I switch tabs? I want websites that are made to be read to optimize for legibility and comfort, not for "not wasting screen space." As I type this comment on HN, the right hand side of the text box where I type my comment is entirely empty. Should the text box be full-width so it fills the screen and doesn't "waste space"? Hell no. It would be a pain in the ass to read my comment as I type it. I don't know about you, but I'm very seldom (never?) reading more than one column of text at a time. Therefore, as I'm reading, anything else on my screen is "wasted". Doesn't matter if it's white space or anything else. It seems like we can't avoid "wasting space." To see the absurdity of that metric, why don't you just make your window as small as possible all the time so you're never wasting any space? Why don't you reduce the font size to 1 pt so you don't waste space with fonts that are comically large? I must admit that logic kind of escapes me, since it misses the most basic purpose behind reading on websites. Now, I'm not unfamiliar with the regular HN comments about how everything is "dumbed down" and it's all about "information density" and cramming everything in one screen should be the be all and end all of design. Unfortunately that opinion also seems to emanate from people who can't substantiate their preference with anything else than appeals to "power user" aesthetics, with very few actual use cases justifying it. These are mostly ego-based arguments I tend to dismiss when discussing design decisions. What does a screenful of text allow you to do that you can't do with a better proportioned column of text? Unless you're the Flash, in my experience, absolutely nothing. As far as saying the experience of reading properly should be left to the user/reader, I simply disagree. I'd rather benefit from the skills of designers and typographers presenting the content for me in the best manner than relying on hacks like resizing my window to get a decent experience. I don't expect to go to a restaurant and be thrown ingredients for me to customize them _my_ way, I want my food cooked deliciously. And I want my content formatted properly and elegantly. P.S. Note that your argument is entirely symmetric: if you don't want to "waste space" on a fixed width website... why don't you resize your window?
- jbay808 6y agoThat might be in part because survivorship bias substitutes (in a good way!) for consideration. For example, if a hundred new bakeries open each year, each one baking bread according to a recipe that the baker just kind of randomly put together without much thought, and ten years on, one of those bakeries is now drawing customers far and wide and five-star reviews, it makes sense to carefully consider any changes to the recipe even though it was only randomly thrown together in the first place. It might just be a winning formula that is the secret underlying their success. Of course it might be their customer service, their casual atmosphere, or their good location that has driven that success, not the bread recipe. But it's hard to know for sure. So changes need to be done very carefully if at all!
- komali2 6y agoNot only does wikipedia need to concern itself with highly established user flows ("sure it's not perfect but at this point I'm used to it" * millions of users), but I think a project like Wikipedia is A Genuinely Important Thing and therefore can't afford to fuck around with UI "experiments" like Reddit does and like Digg catastrophically tried. Trying to both provide a free online encyclopedia of Pretty Much Everything We Know and make it available to as many humans as possible, while also doing UI experiments on those users, seems too ambitious. Let reddit and facebook and google turn their users into lab rats. In ten years Wikipedia can take one or two actually useful bits of information generated from those experiments and implement them, as they're doing here.