Slashdot Mirror


Why Is Wikipedia So Ugly?

Hugh Pickens writes "Megan Garber writes in the Atlantic that aesthetically, Wikipedia is remarkably unattractive. 'The gridded layout! The disregard for mind-calming images! The vaguely Geocities-esque environment! Whether it's ironic or fitting, it is undeniable: The Sum of All Human Knowledge, when actually summed up, is pretty ugly.' But Wikipedians consider the site's homeliness as a feature rather than a bug. 'Wikipedia has always been kind of a homely, awkward, handcrafted-looking site,' says Sue Gardner, executive director of the Wikimedia Foundation, adding that the homeliness 'is part of its awkward charm.' Facebook, Twitter, and Tumblr have built followings in part because of their exceedingly simple interfaces. Everything about their design says, 'Come on, guys. Participate. It's easy,' while Wikipedia, so far, has been pretty much the opposite of that. 'The free encyclopedia that anyone can edit' might more properly be nicknamed 'the free encyclopedia that any geek can edit.' This is particularly problematic because one of the Wikimedia Foundation's broad strategic goals is to expand its base of editors. While the editing interface is friendly to the site's super-users who tend to be so committed to Wikipedia's mission that they're willing to do a lot to contribute to it, if Wikipedia wants to make itself more attractive to users, a superficial makeover may be just the thing Wikipedia needs to begin growing in a more meaningful way."

370 comments

  1. Simple is not ugly. by Anonymous Coward · · Score: 5, Insightful

    Most websites that look awesome have almost no content which is hidden on several pages with lots of ads in between. No thx like it simple.

    1. Re:Simple is not ugly. by del_diablo · · Score: 5, Informative

      Indeed. I don't get the article at all, what is there to improve on? The layout works, there are images when needed to be informative. The only flaw is that some times it can be hard to find a spesific topic even with knowing a few keywords.

    2. Re:Simple is not ugly. by runeghost · · Score: 5, Informative

      I agree. I've never had a negative thought about Wikipedia's look. I like the way it looks. It's clean, useable, and easy on the eyes. It doesn't need anything more. I'd even say it shouldn't add anything more. Clutter is the opposite of information. And the charge that it's difficult to edit is ridiculous.

    3. Re:Simple is not ugly. by Joce640k · · Score: 5, Funny

      If Wikipedia is ugly, what does that make Slashdot?

      By her measure we should all be running away screaming instead of reading useless comments like this one.

      --
      No sig today...
    4. Re:Simple is not ugly. by eulernet · · Score: 4, Insightful

      Adding images will also increase the bandwidth costs.

      An encyclopedia is not a dating site !

    5. Re:Simple is not ugly. by dreamchaser · · Score: 5, Insightful

      Most websites that look awesome have almost no content which is hidden on several pages with lots of ads in between. No thx like it simple.

      Exactly. I wouldn't even call it ugly; I'd call it utilitarian. That is a good thing for a tool used to search for knowledge. It also makes it much more readily available to minimalistic and text only browsers without much extra work on the part of the maintainers.

    6. Re:Simple is not ugly. by SternisheFan · · Score: 5, Insightful

      I agree. I've never had a negative thought about Wikipedia's look. I like the way it looks. It's clean, useable, and easy on the eyes. It doesn't need anything more. I'd even say it shouldn't add anything more. Clutter is the opposite of information. And the charge that it's difficult to edit is ridiculous.

      Sometimes, less is more.

    7. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Mod this one up. I think Wikipedia is way better looking than /.

    8. Re:Simple is not ugly. by fluffythedestroyer · · Score: 1

      Although I think your whole existence is a spam I have to agree on you with that one (what ?? me agreeing with him ?? wtf). In comparison, I tried gnome 3, kd4 and unity desktop management and I have to say that I hate it. The way they use the tools is bad...and not simple in lots of way. I hate the design because it's not simple enough for what I need and I think most of the design is considered bloated.

      So I turned my back on those 3 desktop management software and I use XFCE now. This one is very simple, no bloated design. Just what I need. Hell give me the look of windows 3.1 and I'll be happy. Give me Windows 7 and I'll rant and be bitchy all the time (thats what I use at the office..and I ain't happy about that one)

    9. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Wikipedia is extremely difficult to edit if your brain is calcified from refusing to learn anything since you finished school.

    10. Re:Simple is not ugly. by santax · · Score: 4, Insightful

      Slashdot looked really good with the my little pony theme though! So it can be done!

    11. Re:Simple is not ugly. by Dachannien · · Score: 1

      By her measure we should all be running away screaming instead of reading useless comments like this one.

      I tried screaming, but the lameness filter wouldn't let me.

    12. Re:Simple is not ugly. by Hognoxious · · Score: 3, Funny

      Wikipedia's certainly more functional and less bug-ridden.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    13. Re:Simple is not ugly. by ackthpt · · Score: 2

      Most websites that look awesome have almost no content which is hidden on several pages with lots of ads in between. No thx like it simple.

      Yea, tell it! So damn fed up with overcoded, bloated, whizzy and utterly useless websites and pages. Megan can just cram this one. Geez.

      --

      A feeling of having made the same mistake before: Deja Foobar
    14. Re:Simple is not ugly. by Rich0 · · Score: 1

      Yup. I've had more trouble getting twitter to work in Chrome than I care to detail. I'll take standard html over AJAX any day. Sure, if you're building a fancy application I can see the value in AJAX, but to present content, forget it!

      If they wanted to build an AJAX WYSIWYG/M page editor for WP I could see the logic in that. However, the site layout is perfectly readable as it is right now...

    15. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      I think the complaint was that it's not simple enough. It's definitely bad design. But that's of course different from saying it's ugly.

    16. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      OK now you goddamn "I don't care if it works so long as it looks great" idiots have gone too far. Fuck you very much. Wikipedia is the best site on the net. It is what the web was supposed to be before all you "creatives" ruined it.

    17. Re:Simple is not ugly. by N3tRunner · · Score: 1

      Agreed. Opinion article is opinion. There's nothing wrong with the simplicity of Wikipedia's interface.

      Additionally, I'm not certain that I would want the submission process simplified. It's already simple enough that there's plenty of faulty information on the site from uninformed or spiteful editors. What would happen if every assclown in the universe could edit entries without learning a bit of markup code first?

    18. Re:Simple is not ugly. by JWSmythe · · Score: 1

          There's a secret about really successful web sites. It's not how pretty or ugly it is, it's all about traffic.

          Plenty of people have asked me over the years, if I could make a site just like some other successful site. Sure I could. And we could make it the most beautiful site on the Internet, with the best content in the world. Once they have the web site, if they can't get the traffic, it will fail.

          The pretty look has almost nothing to do with the traffic. Sure, Wikipedia is ugly. It gets traffic.

          I worked for an adult company a while back. They were hugely successful, with million of people going to the site every day. People wanted me to make a site "just like it".

          When I had time to burn, I set up a few sites, "just like" successful sites. Then I let them try to make their millions from it. If they were lucky, they made thousands a year. Like low thousands ($1k to $2k).

          The whole thing about having a successful business is dumb luck. There are a few little things, like a good product, at a reasonable price.

          Despite what we all like to say, Wikipedia has a reasonably good product, and the price (free) is acceptable to the users.

          They don't ever have to make it prettier. The demise of Wikipedia will come about when someone makes a better product, at an equal or better price, that does become popular.

      --
      Serious? Seriousness is well above my pay grade.
    19. Re:Simple is not ugly. by cheesecake23 · · Score: 1

      The only flaw is that some times it can be hard to find a spesific topic even with knowing a few keywords.

      Totally agree. But I fixed this by mapping a Google "I'm feeling lucky" search to a Chrome bookmark keyword. Now I just type "w search-terms" and it nearly always teleports me to the right wikipedia page. Like so:

      http://pastebin.com/QX8t1fwS

      (Posted to Pastebin because I can't get the Slashdot message composer to print this correctly.)

    20. Re:Simple is not ugly. by marcello_dl · · Score: 1

      --
      Using Latin is like juggling on a unicycle - done well it may impress, done badly it always looks foolish -- E.A.Blair

      ^ hoc

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    21. Re:Simple is not ugly. by bankman · · Score: 4, Insightful

      Sometimes, less is more.

      It sometimes appears that designers don't get this at all. Some of the least usable sites I have seen in the past couple of years were the desginers' own.

      --
      I feel so sig.
    22. Re:Simple is not ugly. by bankman · · Score: 1

      An encyclopedia is not a dating site !

      One could argue that this encyclopedia wants to be one...or maybe I just misinterpret the gender gap discussion. :-)

      --
      I feel so sig.
    23. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Agreed. I actually wish Wikipedia would tone things down even more, as in removing the background image and as much of the CSS as possible. When I need an answer, I don't care about aesthetics.

    24. Re:Simple is not ugly. by cheesecake23 · · Score: 0

      BTW, this technique is also useful for other sites that have anal search facilities, e.g. IMDB or Rottentomatoes.

      IncidentalIy, I wish Slashdot would allow you to edit your post post-posting ...

    25. Re:Simple is not ugly. by Phrogman · · Score: 4, Insightful

      And often as not more is less. I can't count the number of beautifully designed artistically creative website designs I have seen - which violate all the rules for design and layout and conveying information ever devised, and have zero content worth actually reading - but *my* its pretty. In many ways a lot of modern websites are a triumph of form over function and not much else.
      Wikipedia has a simple layout that works quite well, it is consistent and I think quite easy to read generally. If it takes learning a slightly specialized markup language to encode the data - well then thats a small barrier to entry that might encourage only those who can be bothered to learn how to edit the pages to actually edit the pages.
      If editors were let loose with a wysiwyg editor then Wikipedia entries would be a chaos of inconsistent layout and display and effectively unreadable, in very short order.

      --
      "The first time I got drunk, I got married. The second time I bought a chimpanzee, after that I stayed sober" Arian Seid
    26. Re:Simple is not ugly. by jones_supa · · Score: 1

      It's clean, useable, and easy on the eyes. It doesn't need anything more.

      An inverted color theme could be a nice addition.

    27. Re:Simple is not ugly. by Hognoxious · · Score: 3, Insightful

      I wasn't even particularly aware of the design. Now to me, that means they're probably doing something right.

      But then I'm the kind of person who doesn't wear a beret or have tarpaulin grommets in my earlobes, so what do I know?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    28. Re:Simple is not ugly. by angel'o'sphere · · Score: 1

      I agree. The layout is close to perfect. The only thing up to discussion for myself is a different colour schema.
      E.g subheadlines could have a background colour.
      I doubt there are many people that have trouble with the wiki markup. After all only people who want to contribute need to learn it. And I assume one who wants to contribute is eager to understand how the mark up works.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    29. Re:Simple is not ugly. by Yvanhoe · · Score: 1

      All the content inside is available, expressly authorized to reuse, and basically open sourced. If someone doesn't like the wikipedia layout s/he can fork it or just add a layer on top of it. I prersonally do like it like it is. I even wish sometimes there would be an even simpler layout.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    30. Re:Simple is not ugly. by Guppy06 · · Score: 1

      Having half a dozen banners at the top of every article ("POV!" "Orphaned links!" "Proofread me!" "Locked article!") does not make a page "simple." And I suspect it discourages the "anyone can edit" thing, too.

    31. Re:Simple is not ugly. by Johann+Lau · · Score: 1

      False dichotomy. Wikipedia could not suck balls, and be even simpler. Wikipedia sucks that way because it sucks that way, not because there is any advantage of it sucking that way.

      "Most websites that look awesome"

      So what? Try repeating that sentence, this time saying "ALL websites that look awesome". Bzzz, bullshit.

      And what do ads have to do with anything?

    32. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Agree 100%. Functional is not ugly. I have a 1956 Continental, my nephew thinks it ugly. He likes Fast and the furious type cars, Preferably with LOTS of stickers on them. But then he likes ketchup on a tenderloin steak.

    33. Re:Simple is not ugly. by Deep+Esophagus · · Score: 1

      I lost interest when the author suggested Wikipedia could learn something about a usable UI from Facebook. Facebook, the site that periodically incurs user wrath by implementing random, annoying changes to their UI? Right, tell me another.

    34. Re:Simple is not ugly. by Runaway1956 · · Score: 1

      Quick - I'm to lazy to use Google to find out. WTF is Megan Garber, and how is her opinion relevant to any damned thing?

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    35. Re:Simple is not ugly. by JDG1980 · · Score: 1

      Having half a dozen banners at the top of every article ("POV!" "Orphaned links!" "Proofread me!" "Locked article!") does not make a page "simple." And I suspect it discourages the "anyone can edit" thing, too.

      That's not a technical problem, it's a political one.

    36. Re:Simple is not ugly. by alexgieg · · Score: 1

      It's clean, useable, and easy on the eyes.

      I like the layout too, but I have to partially disagree on the "easy on the eyes", at least when it comes to font size. With current screen resolutions and sizes I find its 13px text somewhat on the "small" side of the scale. If anything, the only change I'd make would be increasing the default to something in the 14px~16px range plus a very small increase in the distance between lines, thus making the reading experience more e-book-like. But that'd be it. Everything else about Wikipedia's design feels right.

      --
      Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    37. Re:Simple is not ugly. by phantomfive · · Score: 5, Insightful

      Not only that, on the Atlantic article, I counted no less than 6 different typefaces, not counting colors, bold, all-caps, etc. If this lady wants to change things, she should start with her own magazine.

      --
      "First they came for the slanderers and i said nothing."
    38. Re:Simple is not ugly. by Teancum · · Score: 1

      If you really want to have custom color schemes and some crazy formatting, you can always register your own account and select from several different themes that are already pre-built, or for the very adventurous try to roll your own. The bitching is about the default interface, which is kept rather ordinary.

      If you want to see some wild and crazy layouts which can be done with the MediaWiki software, spend some time with the Wikia websites. Some of them are mundane, but there are some really crazy ways to add content that involve moving the buttons almost everywhere and doing some interesting things with the CSS scripts too.

      On top of that, Wikia has been experimenting with the WYSIWYG interface for more than a year now, and in spite of that interface it tends to cause more problems than it is worth other than marking somebody as a "noob". I suppose that helps after a fashion to know who to watch out for that might just screw things up, particularly when you are a project administrator.

      By far and away I see a whole bunch of people that simple need to learn not the wiki markup, but simply how to write the English language (or whatever language they choose to use for contributions including Klingon). Most of the new contributors that are struggling with the markup language also need some remedial writing classes to figure out how to write content of any kind, much less need some hand holding on how to put that content onto a page of any kind.

    39. Re:Simple is not ugly. by jez9999 · · Score: 1

      Indeed. I don't get the article at all, what is there to improve on? The layout works, there are images when needed to be informative.

      Which, to a "UX expert", are all red lights that a visual refresh is long overdue!

    40. Re:Simple is not ugly. by FatLittleMonkey · · Score: 1

      If editors were let loose with a wysiwyg editor then Wikipedia entries would be a chaos of inconsistent layout and display and effectively unreadable, in very short order.

      Yeah, I had that thought. The solution is to "version" the edits from the wysiwyg users. They already created a system for hiding new changes from the viewable page until they is verified by a higher ranked editor. Just turn that on for the wysiwyg editor.

      "Thank you for contributing to Wikipedia. Your edit is awaiting moderation.
      Do you want to be notified when this edit is approved? [Y/N]"

      The alternative is to simply exclude them. Given the choice between "careful introduction" and "snobbish exclusion", I'd prefer the former.

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
    41. Re:Simple is not ugly. by cpu6502 · · Score: 3, Informative

      I just type "wiki Desired Item" into the google bar. It works much better than wikipedia's built-in search.

      As for editing: Wikipedia's main problem is too many markups. People italicize or bold things that don't need it, or list a long overly-detailed source when all they needed was a simple external link. When I edit the encyclopedia I use plain text as much as possible, and keep any markups as simply as possible, so the lay reader can edit it.

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    42. Re:Simple is not ugly. by davydagger · · Score: 1

      yet another irrelivant english major dumb fuck.

      http://www.niemanlab.org/author/mgarber/

      what the fuck does she know about computers?

    43. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Sometimes, less is more.

      If less is more, think how much more more will be !

    44. Re:Simple is not ugly. by Anonymous Coward · · Score: 1

      Warning: Pleasing aesthetics may interfere with your ability to interpret information.

      *Remember the "flashy thingy" from Men in Black?*

      Edward Tufte has plenty say about this in his books. He has a lecture circuit as well, one stop along the way is Seattle, 23 July, in case you Microsofties need some pointers on declutterification.

      His focus is on presenting information, and he lambasts the corporate brand mentality for subjugating content to elevate brand.

    45. Re:Simple is not ugly. by Anonymous Coward · · Score: 1

      Not only that, but slashdot was way ahead of the curve when it came to appealing to a "brony" audience too -- a double win!

    46. Re:Simple is not ugly. by arth1 · · Score: 1

      Agree 100%. Functional is not ugly. I have a 1956 Continental, my nephew thinks it ugly. He likes Fast and the furious type cars, Preferably with LOTS of stickers on them. But then he likes ketchup on a tenderloin steak.

      Kill it. Kill it with fire.

      Yes, the new generation often has different priorities than us. That's to be expected. To me, the new generation seems to like condensed information, flashy presentations, automated sharing, and form over function, while my generation preferred abundance of information, subdued presentations, privacy and function over form.
      Undoubtedly, they are going to win. But they need to keep two things in mind: We aren't dead yet, and there are more of us than them. When they grow older, they will undoubtedly shake their heads at their offspring, and how the newcomers might appreciate raw data over presentation. And again, they will hold on to what makes sense to them until they are a minority.

    47. Re:Simple is not ugly. by Mashiki · · Score: 1

      Well, if it looks really good with the my little pony theme. Just think what would happen if we went with My Little Brony theme. Flaming skulls everywhere, fist bumps on every page. It would be epicness, and testosterone everywhere.

      My god...the page hits and ad revenue we could generate. QUICK SOMEONE GET ME SQUEEGEE! Maybe they actually should do this for April 1st next year.

      --
      Om, nomnomnom...
    48. Re:Simple is not ugly. by gmanterry · · Score: 1

      Indeed. I don't get the article at all, what is there to improve on? The layout works, there are images when needed to be informative. The only flaw is that some times it can be hard to find a spesific topic even with knowing a few keywords.

      I have always felt that there needed to be more images to more clearly explain content. I always thought the images were not included because of fear of copyright infringement.

      --
      Since when is "public safety" the root password to the Constitution?
    49. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      > Sometimes, less is more.

      But, but... GLOSSY BUTTONS! GRADIENTS! ANIMATIONS! FLASH!

      (and here are a bunch of lower case letters to attempt to fool the filter because it is giving me an error telling me not to use so many caps because it is like yelling which is a bit aggravating because i was attempting to be sarcastic by showing excitement through yelling so pbbbbbbbbbbt, take that you mean old filter)

    50. Re:Simple is not ugly. by Velex · · Score: 1

      By far and away I see a whole bunch of people that simple need to learn not the wiki markup, but simply how to write the English language (or whatever language they choose to use for contributions including Klingon). Most of the new contributors that are struggling with the markup language also need some remedial writing classes to figure out how to write content of any kind, much less need some hand holding on how to put that content onto a page of any kind.

      This. A million times, this. It's never the idea that you denote headings with some ==s or that you emphasize text by putting it ''in these'', but it's the very concept of organized writing that implies!

      These same people, given a WYISWYG always seem to produce complete garbage: random formatting, strange font changes, haphazard spacing, etc. It's not that typing == or '' is too technical, it's that proper grammar itself is too technical. The idea of a complete sentence is just as foreign and inaccessible to them as the idea of a heading.

      I wish I were just being conceited. I think that the only reason that people seem to be getting dumber is that the internet and computers have forced the great majority of people into becoming writers. It turns out that writing is something that takes study and discipline, which are two things that most people just haven't ever wanted to bother with. For the average person, as long as they have food, TV, and sex, average is good enough. And why not?

      Too bad we can't go back to the way it was when the average person did not need to be a writer. Maybe those secretaries taking dictation weren't such a bad idea after all. Can't write? Can't type? Let a professional do it for you.

      --
      Join the Slashcott! Stay away entirely Feb 10 thru Feb 17! Close all tabs to prevent autorefresh!
    51. Re:Simple is not ugly. by Anonymous Coward · · Score: 1

      Agreed its not ugly its beautiful. Simple and efficient. I dont require a bunch of collor and moving images distracting me from what Im trying to read and learn something. Keep it simple! Such a stupid article.

    52. Re:Simple is not ugly. by froggymana · · Score: 1

      Wikipedia is extremely difficult to edit if your brain is calcified from refusing to learn anything since you finished school.

      Perhaps Wikipedia isn't interested in what you have to offer then.

      --
      "To prevent this day from getting any worse, I'll just read ERROR as GOOD THING" 1GJU8xLuDKDxEs4KLf8fAGyptoDsqvEsBT
    53. Re:Simple is not ugly. by skine · · Score: 1

      What need has a jackhammer to be visually appealing?

    54. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      WP 5.1 was the pinnacle of WP, and it was not WYSIWYG... I miss it. 6.0 for Windows 3.* was a right mess :(

    55. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      And guess how much money they just made because everyone had to go checkout how 'terrible' this article is. Lots.

    56. Re:Simple is not ugly. by HyperQuantum · · Score: 1

      Well at least Wikipedia supports UNICODE...

      --
      I am not really here right now.
    57. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Wikipedia is great because it has content. When I see a fancy page I find it hard to read and likely not worth the bother.

      Wikipedia is good looking to my eye. I can find everything. It is readable. There are no background images. It is fast to load since it does not have to load 1,000 different "curved edges" or other image flotsam.

      Slashdot is also fairly boring. You should add background music and flashing images to jazz it up.

    58. Re:Simple is not ugly. by DMUTPeregrine · · Score: 1

      A significant part of why I switched from Yahoo to Google many years ago was the layout of the front page.

      --
      Not a sentence!
    59. Re:Simple is not ugly. by Grishnakh · · Score: 1

      Wikipedia IS difficult to edit... if you're a moron.

    60. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      The font is too small. It used to be larger and actually readable.

    61. Re:Simple is not ugly. by Dahamma · · Score: 1

      I was about to post this, but you summarized it pretty well...

      I generally find Wikipedia very easy to read. I mean, what the hell, it's an encyclopedia, not an ad laden "glossy". The whole point should not be to dazzle you, it should be to inform you, and it does that pretty damn well.

      The author needs to understand the difference between "usability" and "marketability." Not that The Atlantic really has either. If I want something flashy as hell but totally unreadable, I'll go to Wired, thank you very much.

    62. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      This... It's functional and it loads fast.

      And despite that, it still looks prettier than what's here at Slashdot.

    63. Re:Simple is not ugly. by ShanghaiBill · · Score: 1

      The only flaw is that some times it can be hard to find a spesific topic even with knowing a few keywords.

      Go to Google, type in "wikipedia" plus the keywords. The article you are looking for will be the first link 99% of the time.

    64. Re:Simple is not ugly. by datavirtue · · Score: 1

      Uh....the geeks are the ones who maintain the pages. Heaven help us all if non-geeks start editing Wikipedia. I saw an example of this once where someone edited an article on a saint declaring that he was a "pussy." I was cracking up in class, but this is what you get when non-geeks start feeling like Wikipedia is accessible.

      --
      I object to power without constructive purpose. --Spock
    65. Re:Simple is not ugly. by Compaqt · · Score: 1

      Agreed that the default font is too small to comfortably read. Do people actually read at that small a size? Pixel density isn't high enough to accomodate that. I usually Ctrl++ 4 times to get a good size.

      Anyway, be thankful that you can increase the size. The nutty "Facebook Comments" you see on a lot of sites these days don't even let you increase the text size. They want to be cool and small, whatever. What's the reasoning behind preventing Ctrl++ ?

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    66. Re:Simple is not ugly. by Compaqt · · Score: 1

      Not to mention my pet peeve: "This looks like a gallery. Wikipedia discourages collections of random images".

      !@#?

      If I'm looking up, say, a foreign city, I want collections of random images. It gives feel for the city. It's not like they don't have captions.

      Does every image have to be inline with a 5-sentence paragraph (intro, 3 bullet points, and a close)?

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    67. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      I would agree, however in light of them coming out against SOPA and similar bills, I have noticed there bio's have become seemingly more censored, they seem to remove certain content for what I would guess to be fear of lawsuits, despite the fact a lot of what should be included in the articles has already been publicly stated and is a known fact. The site is great in how simple, and easy it is to use. But the content is something this story should have focused on.

      Pretty crappy reporting on something that has been talked about at least a dozen times in terms of a "plain looking web site"

    68. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Most websites that look awesome have almost no content which is hidden on several pages with lots of ads in between. No thx like it simple.

      Exactly. I wouldn't even call it ugly; I'd call it utilitarian. That is a good thing for a tool used to search for knowledge. It also makes it much more readily available to minimalistic and text only browsers without much extra work on the part of the maintainers.

      Neither would I call it ugly either; for its as beautiful as a Leatherman or Swiss Army Knife, they have beauty for their uses and mechanical simplicity. Putting some flash animation or other junk on Wikipedia would be the same as putting rhinestones and glitter on a Leatherman.

      In the same way that the glitter would destroy the gripping teeth on the pliers of a Leatherman; flash animations on every informational website would bog down most browsers, causing the computer to work harder and use more resources. Worse for the environment, worse for the eyes, and causing undue wear and tear on the hardware.

    69. Re:Simple is not ugly. by Anonymous Coward · · Score: 0

      Video quid fecavisti.

    70. Re:Simple is not ugly. by rbrausse · · Score: 1

      If I'm looking up, say, a foreign city, I want collections of random images. It gives feel for the city.

      But it is not Wikipedia's function to display image galleries - just go to Commons (one click away).

      Random example: Augsburg (Wikipedia) - Augsburg (Commons)

    71. Re:Simple is not ugly. by Compaqt · · Score: 1

      That may make sense to you, it surely makes senses to the overlords of Wikipedia, it sort makes sense to me, but it makes no sense whatsoever to the users of Wikipedia, you know "normal people".

      Moreover, the function of the gallery would be to have a representative sampling of the images related to a topic (without necessarily being tied to the text). The commons is every single image relating to a topic, which for a large city could be huge.

      Finally, I see that there's a wikiblurb "Wikimedia Commons has media related to: Augsburg". But that doesn't mean anything to non-Wikigeeks.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    72. Re:Simple is not ugly. by rbrausse · · Score: 1

      either "random images" (your first post) or "representative sample" (as in your reply) - you can't have both.

      And IMO are both of your proposals not within the scope of Wikipedia, images are used to illustrate/support the article; the tie to the text is central for an encyclopedia.

      but I agree, the Commons template is in need of improvement, though I don't see a really useful way: The German version is cluttered (literally "album with images and/or videos and audio files"), the English' one is not self-explanatory.

    73. Re:Simple is not ugly. by Compaqt · · Score: 1

      Re: that-

      Calling a gallery "random images" is Wikipedian POV. I.e., from the Wikiblurb: "This section looks like an image gallery. Wikipedia policy discourages galleries of random images of the article subject"

      However, from the POV of normal people, they are not random images. They are representative images.

      And very useful at that.

      images are used to illustrate/support the article

      Why should that be? Who made up that rule? People (nomal people) come to Wikipedia to get information on a subject. From that user's perspective, they have no particular preference to only read an article, and only view images that support the article. I mean, as a user, why would you avoid looking at city images? Because they "violate Wikipedia policy"? Why do you, as a normal user, care about Wikipedia policy. You only care about getting to know about a subject.

      And a a few simple pictures of a city landscape can convey much more than a lot of text describing the same. The Wikipedian way would require bloating up the articles with textual descriptions just so that some Wikibureaucrat can claim that, yes, the photos do indeed support the text.

      Again, I'm only conveying the POV and interests of real users, as opposed to <del>EU directives</del> Wikipedia policy.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
  2. Comparison to Facebook by fleeped · · Score: 5, Funny

    "There's one thing Wikipedia could learn from Facebook, which is less about attractiveness and more about user-friendliness. Facebook -- and Twitter, and Tumblr, and similar sites -- have built followings in part because of their exceedingly simple interfaces"

    Yes, but at what cost?

    1. Re:Comparison to Facebook by syockit · · Score: 5, Funny

      Intelligence barrier to entry.

      --
      Democracy is for the people; you only vote once per season and we'll do the rest of the work for you don't have to.
    2. Re:Comparison to Facebook by gweihir · · Score: 5, Funny

      At the cost of having everybody mediocre and below in there and loosing anybody smart.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:Comparison to Facebook by Anonymous Coward · · Score: 5, Insightful

      And unlike Facebook, Wikipedia's UI seems relatively stable and bug-free, and to me is easier to use. Wikipedia does a great job at presenting information without getting in the way. It's not flashy and doesn't need to be flashy, and can stand alone on the strength of its sheer usefulness without having to have a lot of useless eye candy. The markup they use isn't particularly difficult to work with either.

    4. Re:Comparison to Facebook by Anonymous Coward · · Score: 1

      losing

    5. Re:Comparison to Facebook by Anonymous Coward · · Score: 0

      When it comes to an encyclopedia, I want it to be written by geeks.

      The selection of contributors by the wikipedia's editing interface's idiosyncrasies seems to work as intended.

    6. Re:Comparison to Facebook by adamchou · · Score: 4, Insightful

      I'd beg to differ with that statement. How much simpler can you possibly get than what Wikipedia has? There are no drop down menus in obscure places you have to find. There aren't a bunch of different settings to look for. Functionality from one page to another is the always the same, unlike all the other aforementioned sites. Wikipedia is the epitome of simplicity. The writer is just delirious.

    7. Re:Comparison to Facebook by Stirling+Newberry · · Score: 4, Insightful

      The big difference between Facebook and Wikipedia, is that Facebook is filled with people trying to be nice to you to spread posts about nothing, and Wikipedia is filled with people trying to be nasty to you to write articles about everything.

    8. Re:Comparison to Facebook by Anonymous Coward · · Score: 3, Funny

      At the cost of having everybody mediocre and below in there and loosing anybody smart.
      So, will you be visiting the new spiced up Wikipedia then?

    9. Re:Comparison to Facebook by tepples · · Score: 1

      How much simpler can you possibly get than what Wikipedia has? There are no drop down menus in obscure places you have to find.

      You mean other than Special:SpecialPages?

      Functionality from one page to another is the always the same

      Special pages don't have talk pages. As a more common case, new users can't edit half the popular pages because they're permanently semi-protected due to persistent IP vandalism. Instead, they have to jump head-first into talk page politics with an {{edit semi-protected}} request.

    10. Re:Comparison to Facebook by Capt.+Skinny · · Score: 1

      There's one thing Wikipedia could learn from Facebook...

      How to look like a MySpace profile, circa 2006? I'm looking at you, Timeline.

    11. Re:Comparison to Facebook by A+nonymous+Coward · · Score: 1

      Accidentally modded as flamebait, so this post is to cancel the mods.

    12. Re:Comparison to Facebook by Anonymous Coward · · Score: 0

      +1 ironic spelling mistake

    13. Re:Comparison to Facebook by FatLittleMonkey · · Score: 1

      You know, slashdot, if modding involved a text-box into which you had to type markup, we wouldn't keep making this mistake.

      <user mod="off-topic" increment-1>

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
    14. Re:Comparison to Facebook by A+nonymous+Coward · · Score: 1

      It happened because I clicked in the box by mistake, then used down arrow to scroll the page, not realizing focus was in the mod menu, and when I clicked elsewhere on the page to shift focus, that's when the javascript kicked in to apply the mod.

      Just a stupid user error. Nothing to get worked up over.

    15. Re:Comparison to Facebook by Anonymous Coward · · Score: 1, Funny

      ...loosing anybody smart.

      "Smithers, release the intelligent!"

    16. Re:Comparison to Facebook by FatLittleMonkey · · Score: 1

      <small voice>I was trying to be funny.</small voice>

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
    17. Re:Comparison to Facebook by gweihir · · Score: 1

      1 of 4 gets it. Not too bad.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    18. Re:Comparison to Facebook by A+nonymous+Coward · · Score: 1

      You can use a bigger voice; I am kinda inept in that dept and only realized the humor afterwards.

      So I'll tell an off-topic joke. Know why Canada is called that? It used to be the Commonwealth Northern Dominions, which is quite a mouthful. So they formed a committee to come up with something better. One member suggested they abbreviate it. C, eh? N, eh? D, eh?

    19. Re:Comparison to Facebook by DrVxD · · Score: 2

      Intelligence barrier to entry.

      Wikipedia has a lower limit; Facebook has as upper limit.

      --
      Not everything that can be measured matters; Not everything that matters can be measured.
    20. Re:Comparison to Facebook by Anonymous Coward · · Score: 0

      I think, it will loosen him enough to lose him.

    21. Re:Comparison to Facebook by byornski · · Score: 1

      True that!

    22. Re:Comparison to Facebook by Anonymous Coward · · Score: 0

      *losing

  3. Why is Jimmy Wales so ugly? by Anonymous Coward · · Score: 5, Funny

    An appeal from slashdot.org - get some hot employees to pose for the photos

    1. Re:Why is Jimmy Wales so ugly? by FatLittleMonkey · · Score: 2

      <flat affect>Apparently they did comparative studies that showed banners with JW received much higher click-throughs and donations than ones with other people.</flat affect>

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
  4. Subjective nonsense by simplexion · · Score: 5, Insightful

    is all this is.

    1. Re:Subjective nonsense by Anonymous Coward · · Score: 1

      Absolutely. Someone should mark the article for speedy deletion.

    2. Re:Subjective nonsense by Dogtanian · · Score: 4, Insightful

      As a Wikipedia contributor and editor, I didn't find the article offensive so much as I thought "I really don't see where she gets that from".

      Had I never used Wikipedia, I'd probably expect it- going by her description- to look like something basic and ugly from 1997. I mean, "Geocities"? It's nothing like the stereotypical Geocities page (garish and tasteless decorations and backdrops).

      I must admit that I hardly ever think of Wikipedia's appearance- it doesn't look plain or boring to me, which would suggest it was underdesigned in the way she implies- it simply isn't a factor. That suggests that they got it right- it's nice and clean, and doesn't distract from the content, while not being gratuitously over-plain.

      No, it's not covered in Web-2.0 shading, and there isn't an excess of distracting widgets. In all honesty, I get the impression that the author is really criticising the lack of *cutesiness*, over-designed attempts to appear friendly with "helpful" candy.

      I'll definitely concede one point; editing is still too technical. I'm a geek, so I'm happy to directly edit markup, add templates with parameters, etc. However, I have thought quite often while doing this that it's almost certainly not friendly to average non-techie users. The visual editor is a step in the right direction, but it still probably needs more. I'm not talking about dumbing down things, simply saying that if something can reasonably be presented in a non-technical way without too much compromise, then the choice should be there.

      Of course, I'd probably rather just edit the markup directly, and I'd want *that* choice to remain too, if it was so wanted. :-)

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    3. Re:Subjective nonsense by ackthpt · · Score: 2

      is all this is.

      The disregard for mind-calming images!

      I think she's off her meds.

      --

      A feeling of having made the same mistake before: Deja Foobar
    4. Re:Subjective nonsense by EnsilZah · · Score: 2

      Surely sir or madam, you cannot be correct.
      She clearly states "Here is an empirical truth about Wikipedia: Aesthetically, it is remarkably unattractive" and I'm sure she wouldn't make such a claim without some sort of double blind study that tests the assertion.

    5. Re:Subjective nonsense by Anonymous Coward · · Score: 0

      Maybe she judged the whole site by looking at the page for "anus".

    6. Re:Subjective nonsense by gmuslera · · Score: 1

      There isnt such thing as "ugly" applied to a thing. Is something relative to the observer, by their own criteria, or of some of the cultures he belongs, from a small circle to the whole world, and, to make things worse, at certain point of the history. Was the wikipedia ugly 10 years ago for the same people? Will be in 10 years?

      I prefer to priorize things on more on functionality or usefulness than in some vague and particular aesthetical view.

    7. Re:Subjective nonsense by JSG · · Score: 1

      I agree with you on every point. I run quite a large corporate intranet on MediaWiki with all the toys added in and I find it functional in appearance. My end users say it it works nicely and are pretty much against me wasting time trying to make it look somehow more "designed". Information is relatively easy to find and it is seriously fast compared to the old SharePoint based jobbie.

      However the lack of a really good editor is a drawback and some of my pages look like line noise, especially the dot graphs and charts. Even with the funky new editor It feels like using WordPerfect 5.x for DOS with the coloured cardboard memory jogging strip over your function keys replaced with some icons.

      We resort to people entering their basic content and then flagging the article for marking up by a pool of editors if they are not able to do it themselves.

      When someone does eventually make wiki markup editing simple enough for non techies then they will be a hero!

    8. Re:Subjective nonsense by Idbar · · Score: 1

      I should have known. Today, a reminder to myself:
      Try not to pay attention to Slashdot articles including question marks on the headline. As they most likely fall into your "subjective nonsense" category.

    9. Re:Subjective nonsense by istartedi · · Score: 1

      I must admit that I hardly ever think of Wikipedia's appearance

      See that? That's called good design.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    10. Re:Subjective nonsense by Dogtanian · · Score: 1

      I must admit that I hardly ever think of Wikipedia's appearance

      See that? That's called good design.

      My point exactly. :-)

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  5. WTF? by Rob+Riggs · · Score: 2

    Wikipedia is beautiful! Besides, do you really want non-geeks editing an encyclopedia?

    --
    the growth in cynicism and rebellion has not been without cause
  6. So ugly? by hcs_$reboot · · Score: 5, Informative

    This is so subjective. As an encyclopedia, I like Wikipedia as it is. Providing that much information, from so many fields, in a homogeneous and pleasantly readable way, keep up the good work ... Of course some design enhancements may be welcome. But ugly? Definitely no.

    --
    Slashdot, fix the reply notifications... You won't get away with it...
    1. Re:So ugly? by Anonymous Coward · · Score: 0

      You're exactly right. It's actually not the content's layout itself that I don't like. It's the stuff that's WP-specific. I'd like to see them take the top menu (the tabs, for edit/read/etc) and put it on the left; take the left menu (main page/contents/etc) and put it on the top; collapse all the (new) top menu items which aren't absolutely essential (e.g. a list of possible languages; just make a dropdown); get rid of the errata boxes (NPOV etc), or at least make them less obtrusive; and collapse the references/external links sections by default.

      If you do all that -- and this is a pretty simple list of suggestions upon which others can doubtless improve -- then the result will be a page that's almost entirely content.

    2. Re:So ugly? by bill_mcgonigle · · Score: 1

      providing that much information, from so many fields, in a homogeneous and pleasantly readable way, keep up the good work ...

      hey, who cares about usability, it should look more like a magazine ad!

      look, shiny!

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  7. It does prove that, by transporter_ii · · Score: 5, Insightful

    If your site has good content, the people will come regardless. Much better than a really pretty site with crap content, in my opinion. Another example here is, craigslist. I can't stand to even load up craigslist. It looks so freaking awful, yet they have made a fortune off that 1995-html1.0-looking crap.

    --
    Doctors destroy health, lawyers destroy justice, universities destroy knowledge, religion destroys spirituality
    1. Re:It does prove that, by rolfwind · · Score: 2

      Craigslist has crap for functionality though. I understand wanting to keep things local although I completely disagree with it, but how hard can it be to do away with the assumption that everyone lives in one of their predetermined zones (or even close to it) and implement a radius search by zip code?

      As it is, it's completely useless to me as I straddle two areas and most listings are too far away. I've tried to buy on there with limited success and little convenience, selling is a excercise in frustration and dealing with a lot of idiots who'll waste your time and are never serious to begin with. About the only use I've had for it was finding a few free items, and I guess other people use it to find fuck buddies or what not.

  8. Functional by Irishman · · Score: 5, Insightful

    This is a complaint I have heard a lot in my programming career. In my own experience, most coders I have worked with are focused on functionality and simplicity; getting as much information out there in as straightforward a manner as possible. Often, this means "ugly" to non-CS people. Personally, I find Wikipedia easy to read and easy to navigate. Sure, it may not have graphics popping out everywhere or things dancing across the screen but when I hit WP, all I want is information.

    Now, could it be better? Possibly. It is easy enough to create a new skin for it and give it some zip but I doubt the team would ever make it a default. WP is meant to be accessed on any device, through any type of connection (although it does have some issues in that department).

    If I want lots of useless clutter, I will go to any number of large news organizations' websites.

    1. Re:Functional by maxwell+demon · · Score: 5, Insightful

      I guess anyone who thinks Wikipedia is ugly will also consider books ugly. Think of it: The typical book has a big, mostly uniform block of text surrounded by unprinted space except for a page number. Most books don't even have images (except on the cover).

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:Functional by mikael_j · · Score: 2

      I do think it's important to distinguish between Joe Sixpack thinking something is ugly because it doesn't have dancing kittens and lots of colors and someone with knowledge of design and user interfaces saying something is ugly because it's needlessly complex and is confusing to anyone who hasn't memorized the entire 217-page manual (the UI manual that is, the actual back-end processing daemon obviously has its own 831-page manual with references to important 3rd party documentation explaining just what it is that the back-end processing daemon processes).

      A lot of times I do hear geeky "CS people" dismiss both of the above opinions with blanket statements about how "non-CS people" just want "graphics popping out everywhere" (I'm not saying you're one of them, I'm just using your words because they do fit quite nicely into how some of these people justify not caring about user interfaces).

      And the manual bit, well I've actually come across "enterprise" software like that a few times. The kind of software entirely designed by business people and developers with a UI so complex (and backwards) that it actually required its own manual to be usable (even though the target user was someone who already understood what the software was supposed to be doing and the terminology used by the software).

      --
      Greylisting is to SMTP as NAT is to IPv4
    3. Re:Functional by Anonymous Coward · · Score: 0

      TFA didn't provide any example or proof of concept of what the UI should be like. It only suggested a WYSIWYG editor for editors but didn't suggest how it should look.
      Whoever wrote the article have no clue about flowing text and different browser sizes.

    4. Re:Functional by alexhs · · Score: 1

      The gridded layout!

      I suppose that Megan means that Wikipedia is too liney.
      The comic also addresses "graphics popping out everywhere or things dancing across the screen" :)
      Better just ignore her.

      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    5. Re:Functional by Feadin · · Score: 1

      It is functional up to some extent, I agree with that. But it's also plain fugly. Too much info cluttered in a single screen is not good. Books are definitely not like that, as they usually have a single column with one single topic per page. If you want to change topic you have to switch to another page. Wikipedia shows too much info in too little space, and that makes it look needlessly confusing and difficult to read. It could surely use some modern techs like AJAX and HTML5 to make it faster and show/hide content on demand as needed by the reader. There's really no need to show EVERYTHING you've got at the same time, that's too 90's and has evolved to more dynamic sites for a good reason. Take Google as an example. How much info and functionality Google has? And yet it still manages to have simple and clean interfaces. Compare the Google front page with the Wikipedia front page and you'll easily see what I mean.

    6. Re:Functional by PaladinAlpha · · Score: 1

      Okay, I'll bite. What would you do with HTML5 or AJAX to improve the Wikipedia experience? For instance, I'm reading the article on cats. What specifically would you do using "modern techs like AJAX and HTML5 to make it faster and show/hide content on demand as needed by the reader"?

  9. Ugly = subjective by Anonymous Coward · · Score: 3, Insightful

    Personally, I think it looks clean.

  10. Wikipedia suppors arbitrary themes. by eggstasy · · Score: 5, Informative

    Go select one or upload your own CSS / Javascript:

    http://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering

    1. Re:Wikipedia suppors arbitrary themes. by Anonymous Coward · · Score: 0

      Go select one or upload your own CSS / Javascript:

      http://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering

      Only geeks (God bless 'em) would think this addresses the issue.

    2. Re:Wikipedia suppors arbitrary themes. by Anonymous Coward · · Score: 0

      It's called the "Stylish" add-on. Like Greasemonkey, but for CSS. Look it up.

    3. Re:Wikipedia suppors arbitrary themes. by Anonymous Coward · · Score: 0

      As if CSS is the cure-all solution for all design problems.

    4. Re:Wikipedia suppors arbitrary themes. by Rakarra · · Score: 1

      Really, it's just a way to take a decent-looking site and make it look like shit, like the various xmms and mplayer skins out there (or pretty much any program with "skin" support).

  11. shift ctrl s by Anonymous Coward · · Score: 0

    The number of sites that 'look great' but are impossible to actually read increases daily. Wikipedia is clear and easy to read. Don't make me turn off or customize the css.

  12. Form vs. function: Many people do not get it by gweihir · · Score: 5, Insightful

    Wikipedia is all function. It is efficient, loads fast, list information well. Improving aesthetics to the detriment of functionality is something seen far too often in the web and it is something done only by idiots. Of which there are many, unfortunately.

    Bottom line: Wikipedia is only for those seeking knowledge. All others, please go away, you are not welcome and your criticism is misdirected.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  13. In other words by Rie+Beam · · Score: 1

    AJAX and scripts that bog down the server and make it inaccessible to chunks of the population. But it'll be prettier...

  14. Ugly, your ass. by ftfsis · · Score: 1

    'nuff said.

  15. Pretty encyclopedia? by snsh · · Score: 2

    30 years ago your typical young kid would say "Britannica is boring. Everyone should use only World Book encyclopedia and only World Book encyclopedia."

    Today a young kid might say you should only use About.com.

    1. Re:Pretty encyclopedia? by brickmack · · Score: 1

      I had never heard of about.com until now, and after a quick look through it, I wish that were still true.

    2. Re:Pretty encyclopedia? by spauldo · · Score: 1

      Wow, it's like you read my mind.

      I used to go through my grandparents' World Books and browse, reading whatever caught my fancy. Same with my dad's old Encyclopedia Americana - I still page though it when I'm at my dad's house running updates on his computer.

      Britannica wasn't friendly to a ten year old. The text was dense and it didn't have as many pictures and diagrams. I used it for science reports and stuff, but I never really dived into it like I did the World Books.

      On topic, Wikipedia seems more World Bookish to me. The text isn't cramped into columns and is generally large enough that it's easy on the eyes. There are relevant graphics that are informative. Most articles are laid out so they have enough information so the lay person can satisfy their curiosity while providing links and more in depth information for someone with more serious pursuits.

      I can't think of a thing I'd change, except maybe add a cookie so that wikipedia.org gives you the language start page of your choice. The main page is kind of useless unless you speak more than one language.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
  16. Wikipedia ugly? by khoonirobo · · Score: 5, Informative

    From the full article :

    Here is an empirical truth about Wikipedia: Aesthetically, it is remarkably unattractive.

    How is that an empirical truth?

    Personally I find the site's design really suited to it's purpose. It's clean, no bright colours or extraneous graphics. The content even though dense is easy to read. It is as far as I'm concerned, perfect for the job it is intended to do.

    Now the article after making this broad unsubstantiated statement makes one and only one specific complaint. That editing wikipedia pages is too complex. I agree, it could possibly be easier but wiki markup is the best we have come up with so far. If you have suggestions on how to improve that. That is concrete steps that can make writing wiki pages easier, please share them, most of us are all agog.

    1. Re:Wikipedia ugly? by Sigma+7 · · Score: 5, Funny

      How is that an empirical truth?

      It's an exact comparison learned by observing Wikipedia from more beautiful websites. Too bad it's a subjective comparison.

      Then again, if that person finds a Wiki page ugly, then he's more than free to use CSS or other stuff to make it look beautiful. perhaps floating elements (already in use), rounded corners, etc. If it remains ugly, then it's obvious that presentation isn't an issue.

    2. Re:Wikipedia ugly? by Stirling+Newberry · · Score: 1

      I know, let's put mafia wars gadgets on the pages and hire the Myspace people for user customizations.

  17. Bizarro world by dingen · · Score: 5, Insightful

    if Wikipedia wants to make itself more attractive to users, a superficial makeover may be just the thing Wikipedia needs to begin growing in a more meaningful way.

    What? Because it looks pretty, people will start reading an encyclopedia? Are you nuts?

    First of all, last time I checked Wikipedia was in the top 10 of most visited websites on this planet. So they seem to be attracting users just fine. And obviously, the one and only thing that matters is the quality of their content. As long as Wikipedia continues to provide great information on basically any conceivable subject, a simple uncluttered layout to access that information is all they need.

    Now I get the impression (also by the screenshot) that the article is mainly talking about Wikipedia's homepage. There might be some room for improvement there, but seriously, who goes to Wikipedia to look at the homepage? It's all about the articles. And those pages simply look fine.

    --
    Pretty good is actually pretty bad.
    1. Re:Bizarro world by MMC+Monster · · Score: 1

      Now I get the impression (also by the screenshot) that the article is mainly talking about Wikipedia's homepage. There might be some room for improvement there, but seriously, who goes to Wikipedia to look at the homepage? It's all about the articles. And those pages simply look fine.

      Exactly. You get the impression that the author is the sort that only buys Playgirl to look at the pictures, rather than for the articles.

      --
      Help! I'm a slashdot refugee.
    2. Re:Bizarro world by Anonymous Coward · · Score: 0

      So they seem to be attracting users just fine.

      Attracting consumers, perhaps. But editing users?

      As long as Wikipedia continues to provide great information

      Wikipedia provides hosting and computational resources. Editors provide the information.

      on basically any conceivable subject

      Except, of course, if it is "not notable" or "too detailed".

    3. Re:Bizarro world by dingen · · Score: 1

      So you seriously think Wikipedia would attract more editors if the site looked prettier? If they streamlined the editting process by designing a better interface for it, maybe that would help. But making the site look less ugly, I really don't see the relevance of that. Especially since Wikipedia isn't very ugly to begin with.

      --
      Pretty good is actually pretty bad.
  18. If it aint broken by a_n_d_e_r_s · · Score: 2

    Please dont dont try and 'fix it'. And by fix it I mean make it worse. Adding alot of visual cute feature that slow down download of page will only make it take longer to download. For all that pay per MB of download - its better the less frills the more information. Lets keep wikipedia as a place with a high signal to noice ratio (SNR).

    I love wikipedias simple and elegant design that puts the fokus on the information available on a page and with a high SNR. Please dont destroy it.

    --
    Just saying it like it are.
  19. Perish the thought... by Akardam · · Score: 4, Insightful

    To paraphrase a favorite character of mine, "... I'm so sick of (article writers like this) I could vomit...".

    Wikipedia has at its core one basic job to do: convey information. Setting aside for the moment the questions of validity of content, sources, spats between editors, astroturfing, etc, the prime question is, how quickly and easily was one able to find what one was looking for and absorb it. This is a task at which I personally feel Wikipedia does a fine job. It is a simple, straightforward visual style that doesn't bolt on any extraneous flash (no pun intended) or style just for flash or style's sake.

    By the way, when the article author compares Wikipedia and Geocities visual style and finds similarities, I'm prompted to wonder where the author actually was when Geocities was in its heydey.

    As for the complaint about the complexities of editing on Wikipedia: Heaven forbid that when editing one of the great repositories of human knowledge, that the editors should take the time required to learn the skills necessary to do so... seriously, if Wikipedia ever "redesigns" itself to appeal anywhere near the lowest common denominator of the Facebook/Twitter/Myspace generation, I quit.

    1. Re:Perish the thought... by macshit · · Score: 3, Insightful

      By the way, when the article author compares Wikipedia and Geocities visual style and finds similarities, I'm prompted to wonder where the author actually was when Geocities was in its heydey.

      Indeed ... if anything, Wikipedia is the anti-Geocities: whereas Geocities was famous for its inconsistency, garish colors, and in many cases, almost complete unreadability, Wikipedia is very consistent and readable (well the form of the articles anyway, if not always the words). This is no easy feat, either, given the many editors and authors, but WIkipedia seems to have evolved reasonably good processes and conventions for moving articles towards consistency. [Geocities, of course, had pretty much zero overall structure or convention.]

      --
      We live, as we dream -- alone....
    2. Re:Perish the thought... by DMUTPeregrine · · Score: 1

      Every single page on geocities was guaranteed to have 1 or more of the following:
      Flashing yellow/orange "UNDER CONSTRUCTION" gif.
      Tiled background
      Blink tags
      Marquee tags
      Dark grey text on a black background
      Yellow text on a white background
      Rainbow text.

      --
      Not a sentence!
  20. SPARKLES, and IN COLOR!? by Anonymous Coward · · Score: 3, Informative

    Uh, no. The appearance is fine as it is. I think the goal of making it more user-friendly for people who may want to contribute edits is a good idea, but I see nothing wrong with plain, black text on a white background, and a simple grid-like presentation. It's simple, to the point, and not distracting. As far as I'm concerned, sites such as Facebook, Twitter, and Tumblr are the ones that are ugly. I mean, sure, they aren't using Comic Sans, but I still think their interface is gaudy.

    For similar ugliness, take a look at the frames filled with fluff around the margins of the linked "The Atlantic" article. Gaudy and distracting with flashing ads, "subscribe now", "facebook" something-or-other, "newsletters", blah blah blah. There's so much crap on the right side of the article that it protrudes way down the page, beyond the bottom of the actual text, where you also find the standard navigation/credits baseplate far at the bottom (so far down that it's nearly useless). Oh, and look at that. If I enable JavaScript I also get a pop-up that renders on top of everything else and doesn't scroll.

    Clean up your own damn site. Then we'll talk about "ugly".

  21. Why it needs to be easier for non-geeks to edit by BradGwart · · Score: 1

    We really need it to be easier for non-geeks to edit so that people can add all the pearls of wisdom they have learned throughout their life, no matter what the quality. Example: Alligators are ornery because they got all them teeth and no toothbrush. [Source: Mama]

  22. wikipedia's just fine. by annumina · · Score: 1

    Haven't these people used encyclopedias before? They didn't have fancy bells and whistles (Britannica, for example, was quite plain) but they did their job just fine - knowledge repositories. I don't see why the virtual, editable version should be any different.

    --
    Dream as if you would live forever; live as if you would die today. -James Dean
  23. Gender Thing. by lobiusmoop · · Score: 1, Funny

    I think it's telling that both TFAs linked in the post are by women. Please keep the creeping feminisation of the media out of Wikipedia!

    --
    "I bless every day that I continue to live, for every day is pure profit."
    1. Re:Gender Thing. by Mystra_x64 · · Score: 1

      Your Trolling skill suffered permanent -2 penalty due to being too obvious.

      --
      Quick way to get 30% Funny 70% Troll: defend Opera browser on /.
  24. Need to pick their priorities by Anonymous Coward · · Score: 3, Insightful

    So Wikimedia needs to make a choice:

    -If they simplify the site to make it more accessible, they will probably build a larger, more diverse population of contributors, and will also probably move Wikipedia some distance down the spectrum from "academically valuable tertiary resource" towards "Youtube comments section".

    -Or they can keep it the way it is, with a relatively small community of dedicated contributors, which has allowed it to become one of the most valuable and extraordinary creations of the internet age.

    Personally I value excellence over political correctness, so I would take the second route.

    1. Re:Need to pick their priorities by Anonymous Coward · · Score: 0

      I hate to break it to you, but a lot of editors are already far beyond "youtube comments section." There is so much pettiness and "territory" seeking on the site already that really damages the site.

      Anyway, there are a lot of things wrong with Wikipedia, but yeah, how "pretty" it is is not one of them.

  25. Less is more by SpaghettiPattern · · Score: 5, Insightful

    What's ugly about a site that at one blink of the eye shows you exactly what you need? A site that is meant to be informative. A site that loads like the wind blows!

    May the rapist web designers stay away from one of the jewels of the internet. Less bloat is more usability.

    --

    I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
  26. SIGH, Function over Form. by Anonymous Coward · · Score: 1

    Enough with iPretty shit, it's an encyclopedia NOT an APPedia.

    The sooner we burn pretty( Models, Socialites, Celebrities ) people who put form over function, the sooner we can have better engineered products.

  27. Megan Garber doesn't value functionality by Anonymous Coward · · Score: 5, Insightful

    Decoration gets in the way of functionality. Wikipedia is probably over-decorated as it is, and adding what Garber wants would make it both slower and less accessible.

    In a nutshell, she's clueless on this topic.

    1. Re:Megan Garber doesn't value functionality by ObsessiveMathsFreak · · Score: 5, Funny

      In a nutshell, she's clueless on this topic.

      Ah! Another candidate for Editor then.

      --
      May the Maths Be with you!
    2. Re:Megan Garber doesn't value functionality by arisvega · · Score: 1

      In a nutshell, she's clueless on this topic.

      Second. It looks to me like she thought (and possibly succeded) into getting her 15 minutes of fame by some good olde-fashioned ranting- wikipedia is a Wiki.

      Plus, the Clothes do not make the Man (or the Damsel).

      --
      The three laws of thermodynamics:(1) You can't win. (2) You can't break even. (3) You can't even quit.
    3. Re:Megan Garber doesn't value functionality by Anonymous Coward · · Score: 0

      > Decoration gets in the way of functionality

      Firefox + Web Developer addon: 'CSS', 'Disable Styles', 'All Styles'

      Then at least the content can be easily read and discovered to be useless without the decoration getting in the way.

    4. Re:Megan Garber doesn't value functionality by Anonymous Coward · · Score: 0

      Funny?

      +5 Informative would be more appropriate.

  28. Is the criticism on information delivery or edit? by Anonymous Coward · · Score: 0

    The summary sounds confused, to me.

    It would seem that the criticisms are more properly directed at the edit/contribute interface, rather than the information presentation.

    But then it is a "wiki" and the interface available for editing a "wiki" is not that of facebook/tumblr/twitter.

  29. No, it's not. by Anonymous Coward · · Score: 0

    Wikipedia is fine the way it is. It's clean, it's fast, it works for what it is. If they do redesign it, as they already have in the past, it should still focus on speed and usability, and not be bogged down by scripts and images to "enhance the user experience". Also, the social comparison is completely unsubstantiated. Facebook and Twitter don't have more followers because it's easier to post -- it's because your posts don't even have to be meaningful, let alone well-researched and neutral (would you really invite the #yolo crowd to work on Wikipedia?).

  30. WYSWIG by xcombelle · · Score: 1

    In fact there is a wysiwig interface on the road wich will make the editing less geeky

  31. First look at yourself by Lord+Lode · · Score: 1

    The website on which the original article is posted also has boxed layout, not-so mind-calming images, some fake popup, and all kinds of annoying mouse hover effects.

  32. Ugly? Realy? by Anonymous Coward · · Score: 0

    Dear god no. One of the best looking sites out there! Why must you gussy up all sites with noise? Can't simplistic form be beautiful too?

  33. Who said that it is? by Anonymous Coward · · Score: 0

    "Why is X ugly/bad?" -- typical stupid american style question to make impressions. Moron, it's not ugly. In order to ask why something is ugly/bad we have first to establish/agree that it is and then ask why. Idiotic "psychology" involved questions.

  34. megan garber by Anonymous Coward · · Score: 0

    could have a pretty face but no brains.

  35. Convoluted anyone? by CrackedButter · · Score: 1

    I consider myself a geek, but I want to edit and contribute when the tools are at least as easy as a wordpress blog. I tried to amend something once and it was a waste of my time. It's not intuitive at all.

    1. Re:Convoluted anyone? by Anonymous Coward · · Score: 0

      It's not intuitive at all

      As it shouldn't be.

      Youtube comments are intuitive to add. Facebook comments are intuitive to add. Look how THAT worked out: they're both cesspools of stupidity. Let's keep the stupid off wikipedia.

  36. Easier to edit means more stupid edits in this cas by Anonymous Coward · · Score: 0

    Easier to edit means more stupid edits in this case - it's not broke, so...

  37. Form and function by Anonymous Coward · · Score: 0

    I notice that the author of the original article fails to provide examples of sites that she finds not ugly.

    Personally, I find Wikipedia pretty easy on the eyes. It's not a web site that makes you say "wow, look at the design!" but, like typography, the best web design is the one that you don't notice and doesn't get between you and the information you seek.

    Let's also not forget that a goal of Wikipedia is to be accessible by all, including people who use old computers and slow dialup lines. Making it "more beautiful" (according to some arbitrary idea of what is beautiful) would make it harder to use.

  38. Facebook's UI is not exceedingly simple... by QuietLagoon · · Score: 4, Insightful

    Indeed, Facebook's UI is too complex and dense for its own good. Profiles that use the timeline are nearly impossible to navigate easily. On the other hand, I do like Wikipedia's simple UI. Simple does not mean useless.

    1. Re:Facebook's UI is not exceedingly simple... by LordVader717 · · Score: 2

      Facebook is horrible. I find myself googling instructions for the simplest functionality. "Geeky" programming is simpler.

    2. Re:Facebook's UI is not exceedingly simple... by QuietLagoon · · Score: 2

      Facebook wants their UI to be difficult to navigate. The more time you spend trying to find what you're looking for, the more ads Facebook can present to you. The time you waste poking around the Facebook UI is actually a profit center for Facebook. Why would Facebook want to make it easier?

  39. working link - Re:Simple is not ugly. by Anonymous Coward · · Score: 0
  40. It's not the site thats ugly. by Anonymous Coward · · Score: 0

    It's the unaccountable admins and their checkuser weilding arbcon thugs. Deletionists are also the real vandals eho delete things even then they are notable and encyclopedic.

    Wikipedia is the online equivilent of a decaying city with a corrupt police force.

  41. Too hard to add pictures by Anonymous Coward · · Score: 0

    If Wikipedia needs improving it's simply to fix the almost impossible system they have of adding pictures. Text is easy. Why are pictures so hard?
    As for the appearance of the site - I like it just as it is.

  42. Considering... by Anonymous Coward · · Score: 0

    ... function is primordial in this case; ... yet aesthetics are not to be disregarded; ... more pics would increase spendings; ... and that decorative elements might add to readability,

    I propose simply the use of a few (e.g. 3) CSS alternatives.

    Keep in mind that too many choices might increase costs. Also, Wikipedia must be democratic by nature and not all browsers can render everything. Just caring about the different platforms&browsers is already somewhat expensive, I think.

    1. Re:Considering... by Anonymous Coward · · Score: 0

      Replying to myself, it appears that Wikipedia already offers CSS preferences -- sorry for the redundancy/ maybe Wikipedia could make it a more easily founded setting...

      Also, not to sound obnoxious or something, but reading the original article I couldn`t help noticing the site ("The Atlantic") is IMHO uglier than Wikipedia! (sorry, it's just an opinion)

      Just a reminder that beauty is in eyes of the beholder.

  43. No. by zapyon · · Score: 0

    According to Betteridge's Law [wikipedia.org] of Headlines this is the correct answer.

    --
    I like my spaghetti with source.
  44. The Atlantic Continues to Publish James Fallows by Stirling+Newberry · · Score: 0
    Among assorted other predictions from this great sage is how Japan would overwhelm the US.

    Then there is the unforgettable scare mongering of Jeffrey Goldberg and torture apologia from Christopher Hitchens.

    Never trust a magazine named after where it gets dumped.

  45. Learning markup by tepples · · Score: 5, Informative

    The PCWorld article appears to claim that the barrier to entry is taking the time to learn wiki markup as opposed to pointy-clicky WYSIWYG bold, italic, heading, and link insertion. (Another barrier mentioned in other articles is taking the time to learn to discuss changes on the talk page to get past a perception of undue ownership, but that's not what this article is about.)

    1. Re:Learning markup by jones_supa · · Score: 5, Informative

      I think it would be still nice to have a WYSIWYG interface. Actually I'm surprised that something like that is not in place already. The thing is, even if you mastered the markup (which is not even hard at all), many pages are a horrible mess to edit. For a quick example, see the source of chapter "Early SSDs using RAM and similar technology" in the "SSD" article.

    2. Re:Learning markup by 1u3hr · · Score: 2

      many pages are a horrible mess to edit. For a quick example, see the source of chapter "Early SSDs using RAM and similar technology"

      You would imagine that anyone interested in "Early SSDs using RAM and similar technology" would be pretty geeky and not fazed by the markup. And obviously the page was crested by exactly such people.

      99% of 99% of articles are just plain text. If you have some facts to contribute, just wrote plain text and you'll be fine. Quite likely someone will come along later and pretty it up. Or if you're really lost, put a comment on the talk page of the article pointing out what you think should be changed and someone more experienced may do it

      Much harder to grasp though are the policies -- verifiability, reliable sourcing -- requiring you to cite sources carefully. People who just know facts and write them can do so, but if anyone reviews it or disagrees, it will be quickly deleted.

      It's not all fun, I've come across a lot of assholes, vindictive jerks, persistent vandals and just idiots. The system is quite resilient and has evolved mechanisms to cope regardless.

    3. Re:Learning markup by JDG1980 · · Score: 5, Informative

      I think it would be still nice to have a WYSIWYG interface. Actually I'm surprised that something like that is not in place already.

      The Wikipedia brass have wanted this to happen for quite some time. There have been extensive discussions on the mailing lists about this. Unfortunately, it's extremely difficult to do from a technical point of view because there is no official specification for Wikicode. The markup format was never defined, it just sort of grew. The only real definition for Wikicode is whatever the PHP parser interprets (and that parser is a pile of spaghetti code). Features like templates and ParserFunctions make a WSYIWYG editor exceedingly challenging to develop without breaking many deployed pages.

    4. Re:Learning markup by thehodapp · · Score: 0

      It's already available at wikia.com (somewhat affiliated with Wikipedia). It's crap. I end up using the regular wiki markup which is much more controllable and looks nicer. It really isn't that hard to learn. And in terms of messy markup, that's because people didn't take the time to clean up their markup. It's easily fixed.

    5. Re:Learning markup by Anonymous Coward · · Score: 0

      I think it would be still nice to have a WYSIWYG interface .....many pages are a horrible mess to edit.

      WYSIWYG is a mess to edit. Markup is the sanest way to go.

      Markup defines is about defining the relationship between items -- if you can't be bothered to think about that, you have no business writing reference material.

    6. Re:Learning markup by grumbel · · Score: 2

      That shouldn't be to hard to fix, it's a Wiki after all. Define a syntax, have the parser check it and spout out "syntax error" messages along the way. Leave it to the users to clean it up. This would also be a nice way to introduce new editors to Wikipedia, as fixing syntax errors is easy and unoffensive, so there is less risk of a revert war.

    7. Re:Learning markup by FatLittleMonkey · · Score: 1

      There are also small changes that would help even users who know the mark-up, not just teh n00bs. Being able to hide or minimise certain elements in the edit-box (or pseudo-render them, replacing a bunch of <ref>{{cites... with just their number [7]), but making those elements uneditable, would make it easier to see and edit the normal text within cumbersome sections. (And solve the GP's problem.)

      That sort of thing can be built upon, to lower the learning curve for n00bs, simplify things for the rest of us (and to make it easier to build wysiwyg functions into the editor, because you're only hiding/minimising/rendering elements that are standardised and understood, the rest stays as raw mark-up.)

      (Another example, Live Preview. A little window that displays the rendered form of just the text visible in the edit box, scrolling and updating as you move through and edit the edit-box text. So you can see what you're doing, as you do it. Next version lets you scroll in the Live Preview window directly, so you can find the part you want in the edit-box. Next version lets you edit plain-text directly in the Live Preview window, then adding simple wysiwyg functions like italics, bold, links, headers...)

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
    8. Re:Learning markup by Chuq · · Score: 2

      Wikia afilliated? No, it is it's own separate, private company. It was founded by people who are involved with Wikipedia but that's the extent of it.

      --
      - Chuq
    9. Re:Learning markup by tkprit · · Score: 1

      Rite of passage.

    10. Re:Learning markup by tepples · · Score: 1

      Whether such a rite of passage is beneficial for coverage of certain subject areas is disputed.

    11. Re:Learning markup by cheesybagel · · Score: 1

      The fact is you can enter text easily. If this was an actual published book the people doing the writing would not be doing layout or proofing either so I do not see what is the big deal. Besides Wikitax is not very hard to learn not to mention that there are style buttons in the editor box.

    12. Re:Learning markup by ameoba · · Score: 0

      The real barrier to entry is knowing what the fuck you're talking about. Picking up some wiki markup is easy if you're not a fucking retard. PCWorld has just proven they're irrelevance by claiming that wiki markup is too hard - send them out to pasture with an iPad and a copy of Angry Birds.

      --
      my sig's at the bottom of the page.
    13. Re:Learning markup by JimCanuck · · Score: 1

      Maybe not having WYSIWYG isn't such a bad thing. Limits the number of people who do not wish to put in any effort from actually doing editing. Allowing people who are actually interested in adding and sharing information to get the job done, while limiting the number of people who'd end up just wanting to use Wikipedia as another web forum.

  46. Functional not Ugly by markdavis · · Score: 2

    Add me to the droves of people also saying that Wikipedia is functional, not ugly. I am sick to death of stupid sites that have crap all over them and no content. Pop up s**t, f***ing animated junk on the sides, irritating mouse-overs, and countless other distractions and things to make the site non-functional and slow to load and use.

    And each year it is getting worse and worse with all the "web 2.0" so-called innovations. And unlike the past where you could block Flash, or limit Javascript, now we have pretty much no control anymore, other than just breaking the site completely. So PLEASE LEAVE WIKIPEDIA ALONE.

  47. Functional is not ugly either. by KreAture · · Score: 4, Insightful

    Don't forget functional.
    Today everything has to look like it has been released by apple or it's ugly.

    I cringe when I see all the resources and battery consumption that go into features like false reflections in metallic buttons on a friggin screen.

    I want a website that is designed for quick lookups to be just that, quick! And, it is!

    1. Re:Functional is not ugly either. by zippthorne · · Score: 1

      An apple designed wikipedia would be even more simplified. In fact, it would probably look something like this.

      It wouldn't be editable, though...

      --
      Can you be Even More Awesome?!
    2. Re:Functional is not ugly either. by Anonymous Coward · · Score: 1

      It would be editable for a yearly fee. And there would be hidden, arbitrary rules about what gets things removed and accounts banned. And occasionally, a well-written article would be replaced with a nearly-identical one published by Apple. Finally, Apple would sue Google for using HTML on their site.

  48. fix the editor first by Anonymous Coward · · Score: 0

    Yes, Wikipedia is ugly., but the real problem is the custom markup language instead of using a pretty WYSIWYG editor or HTML. There is no reason why someone should have to learn another language just to contribute to Wikipedia

  49. Yeah, well... by toudaimori · · Score: 1

    I think Megan Garber is unattractive.

  50. it's called "information", stupid. by Anonymous Coward · · Score: 0

    Wikipedia is a great example of classic no-nonsense information design. Get your fluffy feel-good eye candy elsewhere.

  51. Written by subject geeks or computer geeks? by tepples · · Score: 4, Insightful

    When it comes to an encyclopedia, I want it to be written by geeks.

    I want it to be written by geeks in the subject of the article, not necessarily computer geeks if the subject is not information science or information technology. For example, there used to be (still is?) a perception that articles' "in popular culture" were overpopulated with entries from works loved by the demographic of computer geeks who are willing to take time to learn the markup. When I read a chemistry article, I want it to be written by chemistry geeks. When I read a linguistic theory article, I want it to be written by language geeks. When I read an article on psychology or religion or other social sciences, I want it to be written by experts in the field, not people with a vested interest in discrediting the field.

    1. Re:Written by subject geeks or computer geeks? by fluffythedestroyer · · Score: 0

      Theology is the word your looking for in terms of the experts in the field of religion. Those guys have good knowledge and rather gives a neutral type of information on religion as well since they have intel on more than 1 religion anyway. Anyway, just wanted to tell you about the word...not my opinion on it.

    2. Re:Written by subject geeks or computer geeks? by Rich0 · · Score: 1

      Well, I wouldn't even say that WP is run by computer geeks so much as legal geeks or bureaucracy geeks. Or, maybe people who act like computers. I guess you could call them wikipedia geeks.

      A typical dispute over what goes on with some article ends up having nothing to do with either common sense or the truth, but rather who can twist the greatest number of WP:STUPID-POLICYs to get their way. Having no life helps a great deal as well, since even the tiniest dispute tends to turn into the 100 years war.

    3. Re:Written by subject geeks or computer geeks? by taiwanjohn · · Score: 1

      True 'nuff, but experts aren't always best at explaining their knowledge to non-experts. That's one the few complaints I've heard about Wikipedia, that its technical content is often too technical for non-techies to understand. While I agree that this is often true of Wikipedia, I don't necessarily think it's a bad thing. (But at least it's a more valid complaint than TFA... not "pretty" enough? Sheesh! what's next, Wikipedia with a Unity interface?)

      Wasn't there talk a while back about creating a "youth" version of Wikipedia? What ever happened with that?

      --
      XML is like violence. If it doesn't solve your problem, you're not using enough of it. --AC
    4. Re:Written by subject geeks or computer geeks? by Anonymous Coward · · Score: 0

      I want it to be written by geeks in the subject of the article,

      Yes, but if they're geeks in the subject of the article, they'll have absolutely no problem learning wiki's markup language, even if they aren't computer geeks. It's just complicated enough to keep out the worst of the idiots, but not so complicated that anyone who bothers to look at the page can't figure it out. It won't exclude geeks of any subject in that sense, but it will exclude at least some of the idiots.

    5. Re:Written by subject geeks or computer geeks? by icebraining · · Score: 3, Informative
    6. Re:Written by subject geeks or computer geeks? by Anonymous Coward · · Score: 0

      There's a limit to this, though. When I read an article on homeopathy, I don't want it to be written by an expert in homeopathy, because I think that they're all fools or frauds. If a field deserves to be discredited, then it should be discredited.

    7. Re:Written by subject geeks or computer geeks? by JDG1980 · · Score: 1

      Yes, but if they're geeks in the subject of the article, they'll have absolutely no problem learning wiki's markup language, even if they aren't computer geeks. It's just complicated enough to keep out the worst of the idiots, but not so complicated that anyone who bothers to look at the page can't figure it out.

      There are a lot of people who just don't grok the idea of semantic markup. They need a WYSIWYG interface. Don't mistake lack of understanding of IT concepts for lack of competence in that person's chosen field/profession/hobby. Changing your car's oil may be "easy" by auto mechanic standards, but many of us here, myself included, haven't got a clue how to do it.

      Division of labor is a good thing.

    8. Re:Written by subject geeks or computer geeks? by Anonymous Coward · · Score: 0

      Being knowledgeable in a subject doesn't mean you're going to bother to learn wiki's awful markup control and contribue. That's the point of the article. Try reading it some time. Those that do soon discover that articles have crazy ownership battles where the "owners" have almost no knowledge in the subject and will delete contributes from those more knowledgeable.

    9. Re:Written by subject geeks or computer geeks? by Schmorgluck · · Score: 1

      And for a long time, WP has got a bad reputation among people in the humanities fields. As a result, articles about these fields were seriously lacking, which further confirmed WP's bad reputation. The thing is, computer geeks have an edge about editing the stuff. Sure, MediaWiki's markup system isn't very complicated, but this is speaking from a computer geek's point of view. To many people, including smart people, experts in their respective fields, it can still be intimidating if they are not very computer literate.

      And then there's the fact that many of them were shocked by the huge size of articles on matters like, say, Pokémon. It seemed wrong to them, because they thought about it in terms of a physical encyclopedia, in which the space taken by the Pokémon article would necessarily be to the detriment of more serious matters. It took them time to understand that server space is not nearly as scarce as pages in a dead tree book, and that there wasn't a real rivalry issue.

      Just for fun: the most absurd criticism of Wikipedia I've ever read was from a French woman who complained in an interview that, reading the French article on Plato, she learned nothing from it. Thing is, she's a doctor in philosophy, and an expert in classic Greek philosophers. If anything, the fact that she didn't learn anything from the WP article was good news. I mean, if the article had contained a single piece of data that she didn't already know, it would most likely have been erroneous.

      I don't know when the tide turned, but things are better nowadays, prejudices are fading away as the general population gets more computer-literate, including experts in fields far removed from computer sciences. In fact, it's not just Wikipedia, it's the whole Web, and even the whole Internet. I remember in the beginning of the 2000s, on forums, legal questions could be raised in a conversation, and unfortunately there was no lawyer around to give us factual answers. Nowadays many lawyers have their blogs. I learned a lot, and I really do mean a lot, about French legal system (and some bits about British, American, and various other legal systems – and the underlying principles of legal systems as well) thanks to Eolas, a professional advocate (roughly, an attorney in common law legalese), who holds a blog in which he explain legal matters, often based on news. Over time, he was joined by other lawyers as co-bloggers, some of them advocates (of various specialisations), some of them magistrates. And besides these regulars, he sometimes have guests in various legal professions, including cops. Basically, this blog is the French equivalent to Groklaw.

      Unsurprisingly, at about the same time legal experts started blogging, a project started on French Wikipedia to improve articles on legal matters. Said bloggers, including Eolas, were instrumental in this move. What I mean is, as people go more web literate, the online availability of informations in various fields unrelated to traditional geekdom gets better and better, and it impacts Wikipedia like the rest of the Web.

      The one thing I find frustrating about Wikipedia is that, as a computer tech, my main field of expertise is very well covered, so I have limited opportunities to contribute. So I just fix spelling and wikilinks, even parentheses, eliminate every exclamation point that isn't part of a quotation (the latter could easily be done by a robot, I don't understand why there isn't one already) and sometimes discuss about correcting the tone of articles. Basically, I'm a wikignome. I can't be much more.

      --
      There's nothing like $HOME
    10. Re:Written by subject geeks or computer geeks? by Hognoxious · · Score: 1

      Wasn't there talk a while back about creating a "youth" version of Wikipedia? What ever happened with that?

      That's something worth doing, if only as a spoof.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    11. Re:Written by subject geeks or computer geeks? by Anonymous Coward · · Score: 0

      Theology is the word you're[sic] looking for in terms of the experts in the field of religion.

      FTFY.

    12. Re:Written by subject geeks or computer geeks? by darkfeline · · Score: 1

      Ah, but an encyclopedia isn't about explaining knowledge to non-experts; it's about presenting information clearly, precisely, and in detail. Most people couldn't make heads or tails of Encyclopedia Britannica, so Wikipedia is even better in that regard. All you need is a clear head and a good level of reading and reading comprehension ability, and perhaps general background knowledge in the subject (and that last requirement can be waived if you're willing to read up on that knowledge on Wikipedia itself).

  52. i have an idea by jsh1972 · · Score: 1

    maybe they (Wikipedia) should make the default font Comic Sans....

  53. Geeks != geeks by tepples · · Score: 1

    There are geeks, and then there are geeks. See my reply to an IP editor.

  54. I only want geeks editing anyway. by Theovon · · Score: 1

    But then I categorize as 'geek' anyone with sufficiently deep and detailed knowledge of a subject that they can write intelligently on a topic. That includes charismatic lawyers.

  55. Ugh. by roka · · Score: 1

    Are scientifc papers ugly too?
    What's your take on improving them, Megan.
    The whole world is intrigued by the insight you gained from browsing social media sites all day.

  56. How is that an empirical truth? by Stirling+Newberry · · Score: 1

    Because it doesn't belong to a publishing empire. Look at all the wasted space that could be filled with ads for adult diapers and instant weight loss elixirs.

  57. betamax by Anonymous Coward · · Score: 0

    Yea, because betamax's superiority alone worked really well. Or let's look at PC vs. Mac - whose design && functionality is selling like hotcakes right now?
    Imo, wikipedia is ugly as sin. It could be designed better. Simpler. Even more minimalist like an art gallery, since all it has are words - its core product.

    As for craigslist, I'd argue they could be making even more money. Unless you live in a very large city, people don't use craigslist as much. The listings (such as Atlanta) are full of false ads and useless crap, not to mention untrustworthy. Craigslist in NYC or Bay area works much better I think. However, in my mind, craigslist as a brand reeks of cheap crap.

  58. Summarizing two different articles by tepples · · Score: 1

    The summary sounds confused, to me.

    That's because it's summarizing two different articles: one about the front page and one about the editor.

    But then it is a "wiki" and the interface available for editing a "wiki" is not that of facebook/tumblr/twitter.

    That's the problem. A lot of people who are experts in the subject of a particular article are not also experts in information technology who are willing to sit down and learn the markup to wikify an article.

    1. Re:Summarizing two different articles by Anonymous Coward · · Score: 2, Interesting

      I remember when the wiki markup was hailed as something anybody could use to edit webpages from the browser. Before wiki, only geeks could put webpages on the web (and even that was not true, there were plenty of editors with a big "upload" button), thanks to wiki it became easy for all.

      Now you make it sound like a wiki being an expert tool for computer scientists.

  59. Wikipedia has skins you know by Anonymous Coward · · Score: 0

    If anyone thinks they can build a better looking front end for wikipedia, I'm sure they are free to do so. Then the form over function crowd can just pic the iWiki skin and be happy.

  60. I have to say... by Anonymous Coward · · Score: 0

    ...while I am too much of a gentleman to call her "ugly" I certainly don't find ms. Garber particularly attractive.

    Just sayin'

  61. Lol? by trifish · · Score: 1

    one of its broad strategic goals is to expand its base of editors

    You must be joking. Several times in the past people tried to change the tagline shown below each article tag from "From Wikipedia, the free encyclopedia" to "From Wikipedia, the free encyclopedia that anyone can edit"

    And each time the attempt failed when some group of assholes with hidden agenda reverted or opposed the change. They actually do NOT want people to know everyone can edit it. That's the whole truth.

  62. Disagree. by superdude72 · · Score: 1

    If I need information about something, I go to Wikipedia before I go to the "official" website. That tells you all you need to know. Wikipedia provides the information you want without a lot of cruft. Nothing ugly about that.

  63. Slashdot has Improved My Vocabulary by stewbacca · · Score: 1

    Thanks to you guys on slashdot, I learned that "monetize" does not mean what the author of TFA thinks. Wikipedia obviously isn't "monetizing" its patrons because the author is using the term incorrectly.

    Also, this is probably a revenue-per-click article, as the premise is that Wikipedia is somehow awful, but then lavishes praise throughout TFA. I hate that crap. I can't opt out of their crappy revenue generation mechanism until I've already generated revenue for them...bah!

  64. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  65. Dealing with incivility on Wikipedia by tepples · · Score: 1

    The Wikipedia community officially doesn't want nasty. If an editor is persistent in being nasty to you, try one of the several dispute resolution processes listed at Dealing with incivility.

    1. Re:Dealing with incivility on Wikipedia by Stirling+Newberry · · Score: 1

      Official positions mean little, passions run high in the wikipedia community, particularly when dealing with one of the many groups who are there to spread the revealed word of truth that just doesn't happen to be documented in the usual sources.

    2. Re:Dealing with incivility on Wikipedia by JDG1980 · · Score: 2

      The Wikipedia community officially doesn't want nasty. If an editor is persistent in being nasty to you, try one of the several dispute resolution processes listed at Dealing with incivility.

      Because that's the first thing a new Wikipedia editor wants to do: deal with "dispute resolution processes."

      Wikipedia politics is one of the encyclopedia's most serious problems. In that sense it is like many other open source projects (GIMP especially comes to mind here). Good advice from the outside is refused or rejected for cultural reasons or because "they're not our kind of people".

    3. Re:Dealing with incivility on Wikipedia by Anonymous Coward · · Score: 0

      If an editor is persistent in being nasty to you, try one of the several dispute resolution processes listed at Dealing with incivility

      Translation: If you're tired of an editor being nasty to you, then change it up and have an administrator be nasty to you instead!

      (I exaggerate for effect. For the most part Wikipedia isn't nasty, but when it is, the typical issues aren't things like personal insults and racial slurs, it's entrenched editors using rules and "consensus" to cudgel those who differ in opinion from them. And in established editor quoting rules and consensus against newer editor who just has an opinion, administrators side with the established, wikilawyering editor more often than not.)

    4. Re:Dealing with incivility on Wikipedia by FatLittleMonkey · · Score: 1

      It's not about being "nasty". It's the tone that is created when the speaker doesn't care about their tone and doesn't realise that anyone else cares, and/or is being teenage-nerd enthusiastic about their own opinion. People who aren't used to it feel like they're being attacked.

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
    5. Re:Dealing with incivility on Wikipedia by tepples · · Score: 1

      Sort of like how the wrong tone in Mandarin Chinese turns almost any question into an insult to the listener's mother?

  66. Dont worry its on the atlantic so it's crap. by StormyWeather · · Score: 1

    The Atlantic is a joke, just look at their business pages. They try to be provoxative , but are in general universally poorly researched, and inane.

    1. Re:Dont worry its on the atlantic so it's crap. by Anonymous Coward · · Score: 0

      And take a look at their ugly and less-functional website (more side-bar fluff than article, and non-scrolling pop-ups? Please. How "geocities" :-)).

      I suppose if she stares at that kind of advertising-laden website crap all day for her news, Wikipedia must appear "ugly" in its simplicity and functionality.

    2. Re:Dont worry its on the atlantic so it's crap. by afgam28 · · Score: 1

      The Atlantic is a joke, just look at their business pages. They try to be provoxative , but are in general universally poorly researched, and inane.

      Not only that, but The Atlantic also has an unnattractive website with a gridded layout! I'm not sure why she's complaining about Wikipedia.

      It's not like the article page has any more "mind-calming images" than a typical Wikipedia article (unless you count a screenshot of Wikipedia, and all the ads :P).

  67. It's about the information, stupid by Rambo+Tribble · · Score: 1

    What makes WP "ugly" to a designer? More than anything, it's the unrelenting density of information. What makes WP great? More than anything, it's the unrelenting density of information.

  68. Her idea of pretty by LordVader717 · · Score: 1

    "Please enable JavaScript to view the comments powered by Disqus. blog comments powered by Disqus"
    Large portions of the internet have become inaccessible from my "netbook" Dell mini because of the explosion of JavaScript websites in recent years. A simple text-based website will freeze and crash a computer which will happily run beefy IDEs and other fairly resource-draining programs.

    The problem is that the web developers who sit at their 8-processors 16GB RAM machines all day will never know and the majority of people will continue walking the upgrade treadmill simply to use Facebook and gossip sites.
    I thought new web standards would bring us new functionality and smoother experiences, now I wish they'd have just stuck with IE6 and Flash.

  69. UX consultant much? by Hognoxious · · Score: 1

    Here is an empirical truth about Wikipedia: Aesthetically, it is remarkably unattractive.

    What an incredibly stupid statement. Empirically means derived from experiments. Aesthetics is largely subjective (see also: beauty, beholder, eye of) and therefore impossible to measure experimentally.

    So the real ugliness of the site, Gardner notes, isn't cosmetic. It's that Wikipedia has "a built-in bias against design and user-friendliness."

    Another vacuous tart who thinks user friendly == pretty.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  70. User experience issues, not aesthetic by CMU_Ken · · Score: 1

    The problem with the entire article is that it tries to hand-wave over the real issue: user experience. The article basically suggests, "If we put lipstick on a pig, the pig will look much better." This kind of thought process is exactly why there is so much shitty software in the real world... suddenly, everyone is a designer, everyone knows how to do information architecture, interaction design, and visual design. Wikipedia has a problem, agreed, but it is not just a "superficial" one. If Wikipedia was designed with a different kind of end-user in mind (average Joe vs. geeks), it really could enable folks to contribute on a larger scale. However, there's a lot more involved in improving user experience than just making it look nicer.

  71. Why is Wikipedia so unusable? by Anonymous Coward · · Score: 0

    Why do you have to hack in the raw markup like it's 1978? Because Wikipedia grew too large too quickly, and when they realized the UI sucks it was too late to change it. Existing user bases tend to be extremely conservative. Even more so if the site gives them a say. Result is that the original state will be petrified for long after it has been outscaled.

  72. A joke by Anonymous Coward · · Score: 0

    This author is a joke... Certainly an attention whore...

  73. Facebook? by Anonymous Coward · · Score: 0

    Facebook is butt-ugly, complicated, messy, inconsistent, and terribly unorganized.

    Wikipedia is simple, relatively clean, and easy to read.

  74. You mean like The Atlantic? by Anonymous Coward · · Score: 0

    Wikipedia certainly needs more popup ads that cover what you're reading. And a Clippy.

  75. If they change it, people will complain even more by FridayBob · · Score: 1

    Making major changes for the sake of improving its aesthetic appeal is not going to attract more visitors or donors. Likely anything other than very minor changes will irritate more people than otherwise. WP is all about content, even though we may not always be happy about how its content gets there. When people consider visiting the site, only a mindless fashionista will also take the site's look into account.

    Furthermore, Garber's remarks suggest that he doesn't have much of an idea about how WP works. Even if WP had to improve the way it looked to save its own skin, it would probably take years of discussion for them to achieve anything major.

  76. Wikipedia is Not Ugly by ObsessiveMathsFreak · · Score: 1

    Wikipedia is Not Ugly. It has a simple, readable, and dare-I-say even attractive design. It is the essence of quiet typographic design, emphasising content over appearance.

    Which isn't to say that I always agree with the content itself. But like it or not, you have to admit that Mediawiki content is always clearly readable.

    --
    May the Maths Be with you!
  77. my 2 cents by Anonymous Coward · · Score: 0

    who care what it looks like....it's easy to read, nicely organized and consistent! We don't need it chaning formats every 30 days like facebook does...

  78. Refreshing by garyoa1 · · Score: 1

    I find it quite refreshing compared to the vast majority of other crap out there. Maybe I'm old school but I never got the "put everything in the middle and leave the sides blank" shit. It's a page. Use it all.

    --
    Wuddooeyeno? IITYWYBMAD? Like nuts? eclecticallyincorrect.com
  79. No by poltak · · Score: 1
  80. You think it's hard to edit now? by KingTank · · Score: 1

    Just wait until it has some moronic marketing-expert-driven UI overhaul every few months like your typical corporate site. Then nobody will know how to edit it.

  81. Who says it is? by weav · · Score: 1

    The answer is "mu". The question is broken.

    Why do you still beat your wife? Why do Slashdotters hate (country they live in)? Why does the porridge bird lay its eggs in the air?

  82. After three articles deleted by Anonymous Coward · · Score: 0

    After three articles were deleted, I finally said screw it. I will never write a fucking thing ever again for Wikipedia.

    They were not easy to write, I would have been better off spray painting them on the street, at least the delete nazi would have had to spend a day or two cleaning it off. Apparently some people are more important public figures than others. Ironic since later two articles showed up (not by my hand) a couple years later, I was just too early for delete nazi's fat thumb.. It's probably a good thing I don't know where delete nazi lives. Seriously.

  83. If you think it's ugly, fix it yourself by maroberts · · Score: 1

    Create a user CSS stylesheet and change the way you think it ought to look.

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

    1. Re:If you think it's ugly, fix it yourself by Tanuki64 · · Score: 1

      Create a user CSS stylesheet and change the way you think it ought to look.

      Parasite sex. They don't want to do anything. You have to do it for them.

  84. it's functional by Anonymous Coward · · Score: 0

    don't change function over looks...

  85. What does she want? by Jesus_C_of_Nazareth · · Score: 2

    Fair point on the editing set-up. I'm pretty experienced now with wiki markup, but that took time. What's she on about when she talks of "mind calming images"? What's with the Geocities comparison? Wikipedia is a minimalist and utilitarian layout. Geocities was the land that aesthetics forgot, and helped popularise eye-raping text on a tiled background. Really, why did people do that? I wondered if they had a monitor calibrated drastically differently to mine, or did they never read their own websites? How can anyone think that blue text on a starry background is pleasant to read, and auto-playing midi files? God, how did we survive?

    There are plenty other sites she can visit for her modern web experience. Want dynamic stuff that breaks traditional browsing paradigms? Sure, you got it. How about over-use of flash and other crap? Coming right up, albeit in smaller amounts these days due to anyone with an ounce of sense blocking Flash content except for sites where it'll be used to provide the service being sought - not just advertising or "artistic" flair. Want Javascript/AJAX stuff that'll send your cycles climbing, and give you something that looks nice but is in fact far less useful that the old site? Sure, and why not come to Slashdot to see an example of how geeks can build a UI to solve a problem that never really existed - all while neglecting proper support for unicode and touch screen devices. Did anyone at Geeknet not even try browsing Slashdot on a touchscreen device? Trying to adjust filtering is a pain, and why is there an option at the bottom to opt out of the mobile version if it doesn't work? God I hate mobile versions of sites - particularly when I can't opt out of them.

    Ironically The Atlantic reminds me of Wikipedia design. Nice simple layout that doesn't detract from the content. Wikipedia works because its layout doesn't get in my way (except maybe when they fuck around "mobile friendly" layouts.

    --
    JC
  86. Not a problem by Anonymous Coward · · Score: 0

    While I would not call it ugly, there is some room for improvement IMO. Wikipedia beautifier (https://github.com/scotchi/wikipedia-beautifier/wiki/Wikipedia-Beautifier) does exactly what I need.

  87. The disregard for mind-calming images! by SilverJets · · Score: 1

    Is she farking serious?

    If a picture is relevant to the information presented, then sure it should be included. But to clutter up the information (which is exactly what Wikipedia is about) with an abundance of images is just plain stupid.

    Let me guess, when she was a kid she enjoyed the pictures in the books and didn't really have an interest in the words of the story.

    1. Re:The disregard for mind-calming images! by PPH · · Score: 1

      She writes for The Atlantic. Need I say more?

      BTW, I don't like her headline font.

      --
      Have gnu, will travel.
  88. a case of slashdot calling the wikipedia ugly by Anonymous Coward · · Score: 0

    LOLz
    wikipedia contains objective content
    slashdot contain subjective content

    follow your thoughts
    I'm not surprised that an entity that deals with subjective content can't actually see through the forest in their eyes to the outside world

  89. Get off my lawn by equex · · Score: 1

    Did you even have a GeoCities account ? Wikipedia is damn good looking for those who are seeking facts, not bling.

    --
    Can I light a sig ?
  90. It's an encyclopedia. by Anonymous Coward · · Score: 0

    It's certainly functional, and for an ENCYCLOPEDIA that's probably what it should be. Next she'll be saying how camouflage patterns are unbecoming on soldiers.

  91. She is an idiot! by Anonymous Coward · · Score: 0

    The person who wrote this article is a complete moron and probably graduated from a community college "web design" degree. The simplicity and elegance of Wikipedia is EXACTLY HOW WEB DESIGN SHOULD BE!!!

  92. Why is Megan Garber so STUPID ? by Anonymous Coward · · Score: 0

    Wikipedia does not need a redesign.

    Megan Garber needs to find a tall bridge and jump off it. Just be ready for a tsunami when her fat ass hits the water.

  93. That's the point. by Livius · · Score: 1

    As other posters have observed, Wikipedia is functional. Simplicity *is* what counts as beautiful when writing an encyclopaedia.

    There is one big flaw in its appearance, and that is the incoherent mixing of en-GB and en-US spellings. There are so many customization options already, it's ridiculous that there isn't one to consistently give your choice of en-GB, en-GB-oed, en-US, and maybe en-CA, rather than having what 45% or 55% of the world's English speakers will consider misspellings in an otherwise scholarly and professional-quality work.

  94. "I can't use this site, it hurts my eyes" by Anonymous Coward · · Score: 0

    I hear people say this and similar things more and more.

    When I meet people like that I sometimes tell them about a couple I'm friends with. They are sculptors, and work with steel and marble, amongst other materials. They are certainly focused on beauty, that's their profession: both have a sophisticated sense of shape, color and composition, and they make really wonderful things. But somehow they don't mind that their workshop looks messy, they don't mind that their welding equipment isn't beautiful to look at, or their pneumatic chisel, or their angle grinder, or their safety goggles. Their tools and work environment need to be functional, not beautiful, to enable them to make beautiful things. And that doesn't hurt their eyes, they couldn't care less, the notion is ridiculous to them (I asked).

    I point out that computers and software are tools, you use them to get things done, they are like the chisels and grinders. To get things done function matters more than looks, and you can get beautiful results using software that looks plain and uninteresting. I'm an artist myself, I use photographs, math and currently sounds to produce interesting images. I find any software that tries to attract my attention by being (supposedly) beautiful an irritating distraction, I want the software I use to look plain and unpretentious, the beauty is in my own mind.

    I often get blank stares, some people don't seem to be able to distinguish between function and appearance at all. They seem to use software as entertainment and fashion. Tools for social status, I guess, not for getting work done.

  95. wikipedia needs "ease of use for more users" by Coeurderoy · · Score: 2

    like it needs advertisement and a a CSR program....

    The kind of people who might want a more "wysiwig & feel good" content entry interface are exactly the kind of people who do not contribute to knowledge.

    There could certainly be improvement in some elements, for instance I'm sure a plugin to render some biological representation would find some friends.

    But ajax driven emoticon entries ? and maybe "like buttons" .... get lots, or even better go to craigslist and try to criticise them, the CEO reaction would probably be fun to see :-)
     

  96. It's a encyclopedia not a magazine. by Anonymous Coward · · Score: 0

    It works perfect cause you are not in visual overload. Keep it simple, as it works. This is not a magazine where you want color, graphics and style.

  97. Fox News all over again by Anonymous Coward · · Score: 0

    How to drive traffic to your site or network: Take something or someone that is good. Diss it severely in the most opinionated and illogical way. Vigorously stoke the controversy flames. Cash in from page views and ads. Pick something or someone else good, repeat. Goodbye Atlantic!

  98. Re:Women by Coeurderoy · · Score: 1

    The fact that one woman produce a brain dead article does not permit to generalise to all women.

    Or i'd be annoyed, since you are probably male and either a chauvinistic idiot, or lousy at trying humour, since i'm male also, it would make me ... hem ... nope still does not want an operation....

    And if you look around you'll find lots of marketing people ready to "advise" companies/organisations like craigslist, wikipedia, sourceforge, ... on "how to be more efficient" (usually at the detriment of the users (but with more flash(tm) and lights)) and you'll also find out that it is quite gender neutral...

    Of course you can creep back into some hole and say that they are all not true scotsmen...

  99. What Wikipedia Needs by cashman73 · · Score: 1

    Taking a clue from the Slashdot Playbook of Web Design, what they need to spruce up their site is, "OMG PONIES!!!!!!!!!1"

  100. Simple is beautiful -- just not on a tablet by ansak · · Score: 4, Insightful

    This kind of comment comes from the same kind of morons who brought us the re-tooling, for instance, of GMail. It was great (to use) the way it was. Now I hear nothing (NOTHING!) but complaints about it (or blank stares which when probed yield statements of powerlessness). If the underlying code was ugly, the first update cycle should have been to upgrade the code in a way that none of the users would notice.

    Note to Jimmy Wales: resist the UX-groupthink mob who would tell you to make Wikipedia more tablet friendly. If it's ugly, it's ugly the way the old White Pages were ugly. Ugly and informative. The way a real newspaper used to be ugly (especially the front sections up to where the editorials, letters and Op-Ed pieces lay): ugly, information rich and informative.

    Note to the groupthink mob: if you must make something tablet-friendly, make sure it's still screen friendly during the design before you foist it on those of us who haven't caved-in to constant computing through tablet ownership.

    <quickly hitting submit before going off and doing something real>...ank

    --
    Still hoping for Gentle Treatment...
    1. Re:Simple is beautiful -- just not on a tablet by ansak · · Score: 1

      Sorry... just to be clear "This kind of comment" was referring to the question, "Why is Wikipedia so ugly?", not to parent. I agree with parent 100% and more.

      cheers...ank

      --
      Still hoping for Gentle Treatment...
    2. Re:Simple is beautiful -- just not on a tablet by mwvdlee · · Score: 1

      Since Wikipedia is a great example of separating content from style and is open source, there is no reason Wikipedia couldn't have both the current interface and a new shiny one for people who like new and shiny things.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  101. Re:Women by Tanuki64 · · Score: 0

    The fact that one woman produce a brain dead article does not permit to generalise to all women.

    It does. I am extremely hostile to women. With the same right some of them claim all men are rapists, I take the right to say all women are braindead.

  102. The design could be a lot cleaner by Andy_R · · Score: 1

    With my design hat on... looking at the 'page of the day', I can see quite a few things that could be simplified or made more consistent.

    There are eight links that just say "edit", why not just one at the top? The pictures have all been resized to different widths (and lead to a very unfriendly 'back-end' page when you click them). There's an non-standard icon for expanding pictures (2 overlapping rectangles, not 4 arrows pointing diagonally outwards), but the contents are hidden not with a matching 'x' icon in the corner, but some text, which is inexplicably in brackets, not underlined like links usually are. There's a cryptic green 'lock' icon near the top that doesn't match the small grey style of the other icons. The 'view history' tab should probably be changed to 'article history' to be less misleading. The 'rate this page' and footer parts have a lot of wasted space and could be a lot cleaner. There's no obvious visual cue that the article has ended and the rest is 'housekeeping'. Shifting the categories section before the notes would fix this, and suggest places for the reader to go next.

    --
    A pizza of radius z and thickness a has a volume of pi z z a
  103. Special edition by jones_supa · · Score: 1

    While I mostly like the Wikipedia as it is, one could create a printed book version of Wikipedia with hand-picked premium articles and put some extra punch and layout there.

  104. Sounds like ... by PPH · · Score: 1
    --
    Have gnu, will travel.
  105. Blinken of an eye ... by Anonymous Coward · · Score: 0

    Yeah, the designer's view: The only way of improving Wikipedia is to ADD GODDAMN BLINKENLIGHTS!

    1. Re:Blinken of an eye ... by GrumpySteen · · Score: 1

      No no.. that was the old way they improved sites. These days, the way to improve the site is to convert the entire thing to one huge Flash object that takes forever to load and doesn't have pages that can be linked to from another site.

    2. Re:Blinken of an eye ... by Anonymous Coward · · Score: 0

      And do not forget to make contrast of text and background almost nonexistent, to give it a smooth, stylish, and modern look! (As all /.ers know, RTFA is one of the capital sins, so diminishing the reader's ability of actually conceiving the remaining content is considered a merciful service to the read-, err, visitor.)

      Flash-only/dynamic-content-only sites are so old-school, we successfully fought this trend about a decade ago. But now, everything that counts is user tracking.

      Possibly worst of all are the modern sites greeting me with that special page that I need JS to access anything, including a guide on how to activate JavaScript in "Internet Explorer or Netscape" (sic!). But they don't tell me which of the 10-15 external resources I have to allow in NoScript to get the "functionality" (e. g., content) I'm after. Sheesh.

  106. Why not an official Wikipedia editing application? by k(wi)r(kipedia) · · Score: 4, Interesting

    An online WYSIWYG editor that would allow saving the page layout (and not just the content) would be a mess. Even Google can't quite manage it with Google Docs, which remain simple when compared to the more complex layout possible with even a simple offline word processor like Abiword, much less full-blown suites like Libre/Open or MS Office.

    The better and probably more elegant solution would be to develop an official standalone Wikipedia editor similar in function to an HTML editor, with offline and online capabilities and code and preview modes. Since Wikipedia represents a relatively minute subset of possible web page designs, the Wikipeditor can be forked from an existing free HTML editor like Mozilla Composer.

    Just my lazy weekend thoughts ...

  107. Looks Fine To Me by Anonymous Coward · · Score: 0

    Title says it all. It honestly looks fine to me. And anyone *can* edit it, maybe making a whole new page with sections might require them to look at another page's edit field to see how it works but in general just making changes should be very easy.

  108. Hyphenations by devent · · Score: 1

    I do wish Wikipedia would make use of hyphenations. And I wish hyphenations would just be a Html standard. I mean really, how hard is it? We have an open source hyphenation algorithm since 30 years or whatever.

    Please compare yourself:
    Without Hyphenations
    With Hyphenations

    There are some effords to bring hyphenations to the Web, like the phpHyphenator. Please compare also the showdown LaTeX vs. Word vs. Writer. The Web would have zero point.

    Talking about uglyness. The whole Web is ugly. No hyphenations, no real small caps, no ligatures. From typographic perspective the Web tool a huge step back since Gutenberg first invented the printing press.

    --
    http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
  109. Because they spend all their time in edit wars by Anonymous Coward · · Score: 0

    No time to update the interface.

  110. Do we really.... by Lodragandraoidh · · Score: 1

    Do we really WANT editors who are too stupid to operate the simple interface? It is not rocket science.

    Additionally - the (VERY SIMPLE) markup language is what a WIKI is all about...so making it WYSIWYG would make it NOT A WIKI.

    Read This, and may you'll get a clue (for those who want to change the wikipedia interface).

    --

    Lodragan Draoidh
    The more you explain it, the more I don't understand it. - Mark Twain
  111. The site is not simple to EDIT by anared · · Score: 1

    This is about contributing, not viewing the site. Have you contributed to Wikipedia? Its practically impossible for non geeks

    1. Re:The site is not simple to EDIT by xcombelle · · Score: 1

      I contributed to wikipedia but I'm geek so I'm no qualified for non geek problems can you develop

  112. Re:Why not an official Wikipedia editing applicati by Yvan256 · · Score: 2, Insightful

    The problem with WYSIWYG editors is that the browsers themselves add their own mess of HTML and CSS to the things you edit.

  113. Re:Why not an official Wikipedia editing applicati by mwvdlee · · Score: 1

    "Standalone" meaning "not in a webbrowser". Therefore no more susceptible to the quirks of individual browsers than the current text-based editor is.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  114. Fugly ho by dogdick · · Score: 0

    Megan Garber is pretty damn ugly herself. She looks like the guy fro Mask (with Cher, not Jim Carey)

  115. Re:Why not an official Wikipedia editing applicati by SomePgmr · · Score: 2

    I think what you mentioned about allowing people to create and save too much design is a big deal, and something that would end badly.

    I've done more than my share of sites for organizations, and without fail, any time you give end users real command over design you end up with awfulness. This usually ends up being somewhere on the front page as little news updates, where it's a real eyesore.

    I think smart people saw that coming and did a good job using something resembling an extensive superset of bbcode.

    The site is about information. Photos are great. And more information is great, though I do think a minor barrier to entry is probably a blessing in disguise. A willy-nilly democratization of design, however, seems like a really bad idea.

    Also, I don't think the wiki looks bad. It seems reasonably suited to its job as an encyclopedia. Or maybe I'm just used to it.

  116. Superificial authors by Anonymous Coward · · Score: 0

    Anyone who does not contribute to Wikipedia cause they can't be bothered to spend a few minutes and figure out how to edit an article is a good thing. We don't need any more morons contributing than we already have.

  117. Re:Why not an official Wikipedia editing applicati by arth1 · · Score: 4, Insightful

    The problem with WYSIWYG editors is that the browsers themselves add their own mess of HTML and CSS to the things you edit.

    The problem with WYSWYG is that it's WYSIWYBNAEG.
    Markup != presentation, which web "designers" still haven't gotten into their heads in more than fifteen years of fail after fail.

    And in the case of Wikipedia, it does so exceedingly well because of its simplicity, not despite it. The less cluttered it is, the more the actual information pops to the front, and the more room there is for actual information.

    Those who wants a rounded corner ajax-slowed video blog without all the boring details are free to make them. Don't hijack wikipedia, though.
    You tried to hijack /., but we all noticed how well received that was.

  118. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    True. But I thought of this as the answer to the problem of the best way to implement a WYSIWYG or near WYSIWYG editor for the masses who are daunted by the complex markup. Think of it as a necessary evil. An standalone editor with offline capabilities would definitely be better than something that needs to built into Wikipedia's infrastructure.

    Also, a pure WYSIWYG editor isn't what I have in mind, but someting similar to a dedicated (La)TeX source editor that has WYSIWYG preview capability. You can edit the text directly in preview mode, but to change the layout you need to dig into the code. However, the editor can have functions to automate the creation of, for example, [table][/table] or \list{begin}\list{end}.

  119. non-geeks by Anonymous Coward · · Score: 0

    Do you really want non-geeks to edit articles?

  120. Re:Why not an official Wikipedia editing applicati by grumbel · · Score: 4, Insightful

    Quite true, however just because a full WYSWYG editor would be a bad idea, doesn't mean you shouldn't have something beyond the primitive plain text. Things like ref's make editing the plain text pretty painful right now, as you simply can't read the text properly when every line is interrupted by three lines of ref hyperlinks and link descriptions. The proper answer should be a proper structured view of the text that makes it clear where tags start and stop, but also keeps the text human readable without looking like random markup soup.

  121. Good! by Hartree · · Score: 1

    If it keeps Megan Garber from editing wikipedia, that's a plus in my book.

    If she needs soothing images while reading articles on such uplifting topics as The Thirty Years War or the Rwandan Genocide, she should drop a Xanax and go visit some site loaded with pictures of cute baby animals and LOLcats.

    (Disclaimer: I actually rather like sites filled with cute baby animal pictures and the like, but NOT factual work-a-day sites like wikipedia.)

  122. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    If complexity is the problem, then a possible Wikipedia editor can be restricted to the automation of frequently used functions such as the insertion of templates, photos, tables, citations, or footnotres. Users who use the dedicated Wikipeditor won't be able to fine-tune or fuss over, say, the placement of the photos or format of the citation without digging into the code themselves. Think of it as having training wheels for newbie editors.

    I don't think Wikipedia looks ugly either. The problem is the complexity of the markup serves as barrier to entry.

  123. Re:Why not an official Wikipedia editing applicati by jones_supa · · Score: 2

    Things like ref's make editing the plain text pretty painful right now, as you simply can't read the text properly when every line is interrupted by three lines of ref hyperlinks and link descriptions.

    Exactly -- this is part of what I was talking about when I pulled the example from the "SSD" article some comments above. So, even if you are a MediaWiki markup ninja, that kind of clutter just hinders you seeing the article in whole.

  124. get a grip. by Anonymous Coward · · Score: 0

    'The gridded layout! The disregard for mind-calming images! The vaguely Geocities-esque environment! Whether it's ironic or fitting, it is undeniable: The Sum of All Human Knowledge, when actually summed up, is pretty ugly.'

    Oh go fuck yourself, Article. It's perfectly fine. The only intuitive interface is the nipple.

    "if Wikipedia wants to make itself more attractive to users, a superficial makeover may be just the thing Wikipedia needs to begin growing in a more meaningful way."

    The 'Sum of All Human Knowledge' is not a giant Staples button. If you don't see the inherent contradiction of what you've just said, you've no business doing anything on Wikipedia, anyway.

  125. Have you stoppped beating your wife? by Culture20 · · Score: 4, Insightful

    "Why Is Wikipedia So Ugly?" presupposes that Wikipedia is ugly, and forces that notion on listener/reader. You can get away with posing a question in an article title, but not loading a question.

    1. Re:Have you stoppped beating your wife? by eco2geek · · Score: 1

      Exactly. My first reaction was, "Why is Megan Garber so ugly?" This article's title seemed to be designed to push people's buttons.

      Honestly, has it ever occurred to you that Wikipedia was ugly? Did you ever go to Wikipedia because of the way it looked? And did you ever think someone would get paid for a magazine article about her opinion of how ugly Wikipedia is?

  126. Quality bar by tepples · · Score: 2

    Yes, wiki markup was easier than HTML. But my impression from various comments is that the quality bar has been raised since then. For one thing, there are templates and , which didn't exist in UseMod or Phase II. And for another, "ownership" behavior has become more common with Wikipedia oldfags reverting new additions that aren't already wikified instead of wikifying them.

  127. It's useful by koan · · Score: 1

    The way it is, aesthetics use more bandwidth and create more technical issues.

    Leave it alone.

    --
    "If any question why we died, Tell them because our fathers lied."
  128. The same Eolas? by tepples · · Score: 1

    thanks to Eolas, a professional advocate (roughly, an attorney in common law legalese), who holds a blog in which he explain legal matters

    is that the same Eolas that successfully sued Microsoft over a software patent that IE's ability to download code to handle specific media types infringed?

    1. Re:The same Eolas? by Schmorgluck · · Score: 1

      Nope. His pen name comes from the Gaelic word for "knowledge", just like the company named Eolas, but it's the only connection.

      --
      There's nothing like $HOME
  129. Indeed by frankgerlach11 · · Score: 0, Insightful

    Those who are still in the MS-Office stage of document creation have no business in editing wikipedia. These people mostly have a very shallow view of almost anything, except politics in the corporation. In the "hard" sciences they use LaTeX to do their publications, and that is for a reason. Most people don't have useful knowledge to be contributed to wikipedia over more than two paragraphs, anyway. How hard is it learning how to make a paragraph heading and how to make line breaks ? Real experts in some field (say honey bees) spend thousands of hours in the field and spending a few hours to learn wiki syntax is no big investment relative to that.

  130. Wrong by Anonymous Coward · · Score: 0

    how hard is this

    ==Parenting of Unicorns==
    Unicorns are sensitive little feckers. Their crappy behaviour must be accepted as long as it does not hurt them or other unicorns.

    This is a line break in the parenting paragraph of unicorns. yadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yaddayadda yadda yadda.

    People should start to contribute single paragraphs, as these will survive edits by the "wiki masters" with higher probability. It is dead-simple to do it, if you really desire. Those who just want to apply their shitty powerpoint/word practices are NOT welcome.

  131. Also Wrong by Anonymous Coward · · Score: 0

    This is an encyclopedia, a starting point for people who want to research something. It is not a textbook, not a collection of simpleton science articles.
    If you are really interested in something, you need to go to a library anyway.

  132. Wikipedia isn't ugly...it's plain, as it should be by squash_me_quickly · · Score: 2

    I can't imagine that anyone ever sent a letter to Encyclopædia Britannica Ltd. to tell them "Your encyclopaedia has lots of cool information, but it needs a fancier design, the current one is dull."

    The purpose of Wikipedia is to provide information... aesthetics will waste bandwidth, hard-disk space, CPU resources and most importantly time.

    I know that design is important to some people... many of those are the people who got overly excited when a white iPhone(TM) was launched. So it's white, but it works exactly the same way.

  133. It is also hard by Anonymous Coward · · Score: 0

    ...for people who like to be spoon-fed by their favourite whacko broadcast channel. As we don't need the crap knowledge of fox news on wikipedia, it is good these bozos stay out.

  134. go direct with a bookmarklet, don't even search by spage · · Score: 1

    Since a wikipedia page is http://en.wikipedia.org/wiki/Starting cap word phrase , you can just create a bookmarklet for http://en.wikipedia.org/wiki/%s, assign it keyword 'w', and then type [Ctrl+L][w]Criticism of Wikipedia to jump directly to a page. Even if you guess the page title wrong Wikipedia often has a redirect.

    Also works well for Wiktionary, etc. Some browsers only let you keyword a search form with a query string, but this is fabricating the page's actual URL

    It's a great Mozilla feature. You can't (?) do it on Android, Google wants you to search with them. And keep you in Google rather than jumping to Wikipedia: Google's "Knol" wikipedia competitor folded but now now with Knowledge Graph in search results (seemingly culled from Wikipedia) Google is showing you the quick Wikipedia info without you needing a trip there .

    --
    =S
  135. good point! - Mod parent up by ansak · · Score: 1

    If someone thinks wikipedia looks so ugly, let them do the hard work of designing new CSS suites for what they think should look great

    --
    Still hoping for Gentle Treatment...
  136. Keep off the flowers by epine · · Score: 2

    Note to Jimmy Wales: resist the UX-groupthink mob who would tell you to make Wikipedia more tablet friendly. If it's ugly, it's ugly the way the old White Pages were ugly. Ugly and informative. The way a real newspaper used to be ugly (especially the front sections up to where the editorials, letters and Op-Ed pieces lay): ugly, information rich and informative.

    Even better, visualize this request as Michael Jackson returned from the grave to recommend his favorite cosmetic surgeon.

    There's a lot of people who seem to have trouble distinguishing aesthetics from anaesthesia. I'm guessing what many of these people want is a presentation layer designed by Normal Rockwell on Quaaludes to subjugate any perception of the complexity or messiness of the real world that might disrupt the internal forgetting contract.

    Why should Wikipedia be more beautiful than the world it describes? Wikipedia is only ugly if it fails to describe the world in a way that is quickly intelligible as a workable first hypothesis.

    Beauty is fragile. Beauty announces: Keep off the Flowers.

  137. and The Atlantic is webbug/tracker-ridden hell by spage · · Score: 5, Interesting

    It's ugly, and the fine Ghostery extension tells me that Atlantic page has 15 web bugs and ad trackers from AdThis, Bizo, Chartbeat, Disqus, Doubleclick, Facebook Connect, Facebook Social Plugins, Google +1, Google Analytics, Omniture, Outbrain, Parse.ly, Quantcast, Scorecard Research Beacon, and Twitter Button. Each one of those is another image and/or increasingly, another 10kB of JavaScript crap just so third parties can watch what I'm doing on that page.

    A Wikipedia page: not one.tracker or web bug. "You're beautiful to me on the inside."

    --
    =S
  138. Bigger Question by toddmbloom · · Score: 0

    Why is Wikipedia filled with snobby, elitist editors with an over-inflated sense of self-worth?

  139. Everyone is focusing on the "ugliness" comment by swillden · · Score: 1

    I don't think WP is ugly, and I don't really care. It works very well for presenting articles about topics, and that's what it's supposed to do.

    However, the other part of the complaint, that only geeks can edit it, does have some merit. It's overstated, of course, you don't have to be any sort of techie to figure out how to type wiki markup, but there is a non-trivial learning curve, and it's gotten worse as more features have been added to the markup language. I think it probably is an obstacle to getting people interested in editing.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  140. Re:Why not an official Wikipedia editing applicati by Zontar+The+Mindless · · Score: 1

    The problem is the complexity of the markup serves as barrier to entry.

    I have never understood the *need* for wiki markup. What's wrong with plain old vanilla HTML (the basics of which can be learnt in an afternoon by any teenager of at least average intelligence)? Why all the unnecessary round trips between the two?

    (Personally, I'd prefer to use a subset of DocBook XML, but that's neither here nor there.)

    --
    Il n'y a pas de Planet B.
  141. Low Density Chick by Anonymous Coward · · Score: 0

    Megan is obviously a low density chick - easily sharecropped.

  142. Megan Garber = doofus by Anonymous Coward · · Score: 0

    Megan Garber leave wikipedia alone you vile trendoid wench daemon.

  143. Leave it alone by p51d007 · · Score: 1

    It is an INFORMATION place. It's not suppose to look like a flippin itunes/app store. It's a "virtual" dictionary, so to speak, so just flat leave it alone.

  144. It's Not by cmwatford · · Score: 1

    Looks fine to me. Sure it doesn't have much flare but does an encyclopedia really need it?

  145. Not written by geeks -- written by experts by eco2geek · · Score: 1

    When it comes to an encyclopedia, I want it to be written by geeks.

    I'd rather have articles written by experts in their respective fields rather than written by geeks. "Geek" != "Expert".

  146. Re:Why not an official Wikipedia editing applicati by tbird81 · · Score: 2

    Because it's much easier to type:
    This is a [[link]] and here is a link to a [[different subject]].

    Than it is to type:
    This is <a href="\wiki\link">link</a> and here is a link to a <a href="\wiki\something else">different subject</a>.

  147. After reading her article by Anonymous Coward · · Score: 0

    Wonder what her opinion of theatlantic.com is.

  148. it's a wiki, for spaghetti monster's sake... by unami · · Score: 1

    there are so many things that need to be done on wikipedia - like a more structured approach to information. the design is sparse, and that's a good thing, imho. good design is about usability first, not about fancy-schmancy fonts and graphic design. and even if the minimalistic design weren't a good thing - a new design should be way down on wikipedia's to do list. i can understand the "simple design makes it easier to contribute"-argument. but really - wikipedia's design isn't overly complex or anything. if megan garber or someone else is to lazy to grasp the interface of your run of the mill-wiki, she probably shouldn't be contributing to wikipedia in the first place. maybe she should also think of returning her computer and go back to using a typewriter instead.

  149. It's not ugly. by DL117 · · Score: 1

    It's minimalist and minimalism is beautiful.

  150. Balance, or mush? by justthinkit · · Score: 1

    What kind of web sites would you get if Megan Garber married Jakob Nielsen?

    --
    I come here for the love
  151. Google "your keywords" + " wiki" by justthinkit · · Score: 1

    So you type your "few keywords" into Google, followed by " wiki". Works for me.

    --
    I come here for the love
  152. Simple is indeed better in this case... by Anonymous Coward · · Score: 0

    I like the simplistic layout of Wikipedia. It doesn't detract you from reading the articles with flashing images.

  153. Re:Women by Coeurderoy · · Score: 1

    well, you might want to get some help, being hostile to half of humanity is a bad idea.
    And you correctly assessed the value of your position, it is exactly as valid as the one of the few men eating dragons, that is not at all.

    The fact that some of your enemies might be stupid does not make you smart...

  154. Re:Why not an official Wikipedia editing applicati by Grishnakh · · Score: 4, Insightful

    I don't get this "Wikipedia is Ugly" idea either; I think it looks really good personally. There isn't a bunch of extra flashy crap, just the article text, some tables listing key points concisely, some relevant photos, and finally references at the bottom. Then there's a simple menu on the left, and some tabs to look at the "Talk" page, edit the content, or view the edit history, and a search box plus a link to log in or create an account. What little color there is is muted and very neutral. What's the problem?

    I think this is just a bunch of Web 2.0 morons complaining because it hasn't been completely redesigned and uglified for no reason at all, just like Gmail's crappy new interface; change for change's sake.

  155. Innovation needed by yusing · · Score: 1

    As a longtime Wikian, gotta agree that WP is long-overdue for some interface overhauls. And some imaginative, sort of "3D"-ish (expansive, connection-revealing, ... ??) alternatives for viewing data. It has done well at emulating formatted texts, and taking elementary advantage of hyperlinks, but done very little serious innovation in modern/alternative forms of data-display, in linking, in user-customization and user-world-building ... I could go on and on.

    WP is a wonderful project, and I'm happy to have been a part of it, but I'd really like to see some leadership into taking advantage of all that data in some awesome, mind-blowing ways. Maybe it needs to run a year-long contest with BIG substantial PRIZES for world-class innovation -with graphics- (plug-in?) that enhances insights and utility by an order of magnitude.

    --

    "You must try to forget all you have learned. You must begin to dream." -- Sherwood Anderson

  156. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    Right. Wiki markup is easier than plain HTML for doing footnotes and the like. It's also more semantic (context or sense-based) in that marking, for example, a series of words as a title would autoformat the words as italics. This, of course, can be done using CSS, but the ensuing HTML with styles would become just as complex.

  157. 'wah... wikipedia is ugly!!!1!11!!!!' by Anonymous Coward · · Score: 0

    Just proves that some people will complain about anything.

  158. Simple is fine by Anonymous Coward · · Score: 0

    Sounds more like the author has a problem. Oh well

  159. Simple Answer? by kyrio · · Score: 1

    http://en.wikipedia.org/wiki/Betteridge's_Law_of_Headlines

    Wikipedia obviously isn't ugly at all.

  160. Bitch please! by Anonymous Coward · · Score: 0

    Look in the mirror first

  161. Where to Begin ? by Anonymous Coward · · Score: 0

    >>> "a superficial makeover may be just the thing Wikipedia needs to begin growing in a more meaningful way"
    A: Do you even read your own copy ?
    So, if we do something superficial, something meaningful may happen?
    If I change my desktop wallpaper, do I get more work done ?
    If I buy a new welcome mat, is my house now a home?

    B: Wikipedia will be more welcoming when the majority of posters aren't the worst of homosexuals, atheists, abortionists, socialists, political hacks,
      or well-meaning but essentially clueless twenty-somethings who do not have the mental acumen to write for an encyclopedia.

  162. Re:Why not an official Wikipedia editing applicati by rtb61 · · Score: 2

    When in doubt the KISS principle always wins http://en.wikipedia.org/wiki/Kiss_principle. Keep It Simple Stupid, just like same lame arsed journalist trying to drive page views by targeting well known public identity with some lame pointless attack. This article on slashdot should not just be about the appearance of Wikipedia but also about lame hack journalists on the web trying desperately to drive page views before being fired by writing up inane articles that try to hype the journalist by associating their name with the identity they are targeting.

    --
    Chaos - everything, everywhere, everywhen
  163. Re:Why not an official Wikipedia editing applicati by Compaqt · · Score: 1

    OK. Now, is it easier to type Heading or

    ======Heading=====

    (oh, is that 5 or 6 equals signs?)

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  164. This Makes Me Angry by localman · · Score: 1

    Just reading this makes me angry. We've got this amazing volume of content in a highly useable, incredibly clean and completely unobtrusive format... and your complaint is that it's ugly? Fuck you. I don't know exactly why it makes me that angry, but it does. Probably something to do with the vast swaths of people who can't tell the difference between pretty and quality.

    Why don't we got back and take Shakespeare out of this awful line-by-line format and make it all swirly or something? Moby Dick needs to be printed on pages with a water-texture background. Black readable text on a white background, cleanly segmented by content? Oh god, the graphic designer in me is just aching to jump in and fuck it all up.

    Sigh.

  165. Re:Why not an official Wikipedia editing applicati by Compaqt · · Score: 1

    Doesn't Wikipedia have a little toolbar like most wikis where you click on h3 and it ouputs
    ===Enter text here===

    ?

    If so, what's the problem?

    If not, that would be nice.

    I don't think Wsyiwig would quite work because Wikipedia has a lot of semantic markup (like the dreaded Citation Required).

    So, from my perspective Wysiwyg would be a disaster, but a markup helper would be useful.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  166. This is hardly surprising-- by Anonymous Coward · · Score: 0

    Leave it to a broad to attempt to devalue something of utmost value and use (and entertainment and amusement) because it (to paraphrase) "isn't pretty." Is she American? It would hardly be surprising because that lot are nothing but superficial and watch reality on telly because they refuse to recognize it all around them.

    Wikipedia is "unattractive," I assume, because it gets to the point and presents its information clearly; would that the same could be said for the female of the species.

    Leave it alone. If you don't like how it looks, slag off.

  167. Yes man, Beauty is in the eye of the beholder. by bobs666 · · Score: 1

    What do you want a trash CSS like Slash dot. Slash Dot looks better if you turn CSS off.

    HTML was written so people could publish there papers online. But HTML has gotten so ugly under the hood most people would not could not publish a paper in HTML.

    People have lost sight that in the fact that simply is is beautiful. Ask any physicist. About the Beauty of a simple equation .

  168. it's not by kdemetter · · Score: 1

    Wikipedia is not ugly.
    It has an interface suited for it's purpose : providing concise information on basically anything.

    When just looking for information, you don't want a super slick colorful interface, that's just going to distract you, and waste your time.

    Also, having a lot of different content, it's kind of necessary to have a light interface that works with all content.

  169. Re:Why not an official Wikipedia editing applicati by maglor_83 · · Score: 2

    On the desktop, it's mostly pretty good, although tables can look a bit poor when not done well. On the mobile, I would go as far as to say it is the single best looking site I've seen.

  170. Good thinking. by Minwee · · Score: 1

    So let's get started. Now, should The New Wikipedia have a spinning logo, or a flaming logo?

  171. Re:Why not an official Wikipedia editing applicati by brunes69 · · Score: 1

    It's not THAT difficult. There are all kinds of WYSIWYG edtiors for wikicode already! The fckeditor plugin for mediawiki is one example, TinyMCE is another, and there are other examples as well.

    Yes, none of them are perfect, but that is partially because they have no champion project backing them. If Wikipedia adopted one of these, they could make it "perfect enough" in very short order.

  172. Here is an empirical truth about Wikipedia: by Anonymous Coward · · Score: 0

    If you analyze it long enough it seems the words "empirical truth" does not have a meaning. As far as I reckon the truth is illuminated by what is empirical. What is not true can be illuminated by what is empirical, but in my estimation empirical information is always used to illuminate the truth. Wtf are you talking about ma'am ???????

    Based on the context, I am assuming she is saying Wikipedia is ugly because it doesn't look like all the other sites. Look at every modern site, and the empirical truth arrives. Wikipedia does not look like that. If it doesn't look like everything else it is therefore ugly. I can hear her shrieking now "nooooo thats not what I meant."

    The article is a fucking mystery. I think the author is playing some weird game.

  173. Megan wouldn't know design even if it bit her ass by r_batty_00 · · Score: 1

    Megan Garber is being destroyed in the comment section of The Atlantic. There are nearly 50 comments... all of them pointing out how clueless she is about design, how Wikipedia is actually well laid out, that she doesn't know what an empirical truth is , etc...

    Oddly enough, Wikipedia has some interesting info on The Atlantic-

            "In 2010, The Atlantic posted its first profit in the last decade... was the result of a cultural
              transfusion, a dose of counterintuition and a lot of digital advertising revenue."

    It has already been suggested in the comments that she may be nothing more than a comment troll.

    If you found Megan's article to be insightful, be sure to read her similarly penetrating articles:

              Taco Bell vs. Old Spice: The Twitter War That Wasn't
              Here Are 10 GIFs That Will Restore Your Faith in GIFs
              'New York Times' + Buzzfeed = OMG

  174. Wikipedia is beautiful by Anonymous Coward · · Score: 0

    She just needs to take off her glasses in an 80s teen movie nerd-to-hot-girl sequence.

  175. But it is! by vuo · · Score: 1

    Since this whole Slashdot comments page has - expectably - become a giant circlejeck, I beg to differ. Wikipedia's default themes are all hard on the eyes. The text is too small, and there is no easy option to set a black background. I positively hate the obligatory bright white background, DOS-style fluorescent-on-black was much better. Wikipedia has already given in to a certain 1999's style "fashion". Also, the markup is a kludge.

    In fact, I like the mobile site. That, and no limitations on use (the mobile view has limited functionality), it could be better.

  176. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    I like Wikipedia the way it is. However, some people (sorry for the weasel words) want to turn it into a WYSIWIG platform that rivals Google Docs. If that's the intention, then I think it would better to leave Wikipedia the web site alone, and dump the WYSIWIG editing onto a standalone application. The standalone app would be capable of reading all official Wikipedia "tags" (if that's what it's called) and have something like the W3 Consortium's Tidy to clean up or beautify (in a structural sense) bad or human unreadable markup.

  177. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    I was thinking more of a program that can be installed in the user's computer. But, yes, blessing an existing project would help it gain traction and would be better than starting a project from scratch.

  178. Re:Why not an official Wikipedia editing applicati by Compaqt · · Score: 1

    I wonder if the markup generated by the tool would be so bad that bad markup would drive out good. I.e., the markup would be so bad that people wouldn't want to wade through it manually anymore.

    More generally, regarding wikis that you use privately, am I the only one who thinks that wiki markup is not really that intuitive or easy? I wrote a manual once in DocBook (an SGML format), and I found that easier than some of the wiki markup which you have to lookup and check before using it.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  179. Re:Why not an official Wikipedia editing applicati by k(wi)r(kipedia) · · Score: 1

    Semi-WYSiWYG is probably the way to go, similar to TeX editors with preview and helper modes. I find Wiki markup when HTML code is embedded into it. Also, I see far too many kinds of delimiters when compared to HTML or even TeX. This appears to be the byproduct of a design where delimiters are doubled characters like [[ or == versus the mostly single characters of TeX like \ or { or HTML's < or / (with the notable exception of the comment block markers).

  180. Isn't Wikipedia licensed under a CC licence? by slyguy135 · · Score: 1

    So anyone can go ahead and make a "beautiful" version of Wikipedia, right?

    What's that? Oh, the curious sound of crickets mixed with tumbleweed.

    (But I do wish it was much easier to correct very minor mistakes, like typos, just by clicking on the text to make it editable, like the descriptions under [one's own] Flickr photos).

  181. I can't make up my mind... by Anonymous Coward · · Score: 0

    Interesting? Informative? Insightful? Funny? Flamebait? Off-topic? Overrated? Underrated? Troll?

    Decisions, decisions...at least it's not redundant.