Best website, EVAR! Minimalist design, most basic browser will see it’s content. Content is king. Pretty graphics are not part of that content.
That is what you should be aiming for. Their color scheme could use some work, but you won’t see that with a basic browser. All you’ll see is the content. If your content sucks, Avatars, Likes, Animated GIFs, Facebook crap, and Twitter tweets won’t improve it.
The mistake you make is assuming that delivering something via the web is a promise to deliver it to all web clients. Many web sites are merely applications, and a subset of browsers just happen to be the convenient platform for the developer to deliver them on. You can write a windows application and use very specific APIs to do something incredibly mundane, and then one day you realize that it would be a lot less work if you used HTTP and Internet Explorer to deliver the exact same functionality to the exact same audience with a lot less effort, but what you’ll end up with is a certain segment of individuals who will see that choice and say “WHY DON’T YOU SUPPORT OPERA.” The answer, of course, is “because screw you, the alternative to building a web app that only supports certain browsers it to not make it a web app and make it support an even smaller number of users.”
To some people, the web is a tool to accomplish a task, and to some, it’s some kind of ideologically pure concept where if you are on the web you must support all of the web users. It basically takes the ability to build nice, rich, web-based things and converts it from an asset into a liability due to the fact that you are expected to support the lowest common denominator while still trying to do advanced things that are only available to some clients. I’m thankful that the number of people who think like this is rapidly dwindling, and I’m also thankful that I don’t need to support IE6 anymore.
Uhhh … do you realize that those updates are often bug and security fixes, which make the newer versions of browsers faster and more stable than previous versions? The Firefox 3.* series had a bad reputation for memory leaks, which was patched through the years, but finally fixed in Firefox 15. The various security holes of Microsoft Internet Explorer 6, and the stubborn resistance of many of its fans to upgrade it, remains a thorn in the side of Microsoft, IT security professionals, and Web designers.
Nobody’s fixing the bugs in your old browser. Those newer versions are the fixes, the “kinks being worked out”.
With a well-designed web page, you don’t need to actively support IE6 or Mozilla or Netscape Navigator or whatever. You just need to support HTML, and if you do that, then all browsers will automatically work with it.
Now, again, there might be some fancy things you want to do that require advanced features not available on all browsers. And if those fancy things are themselves your content, fine, go ahead and require those advanced features. But for basic purposes like displaying plain text, it’s easy to support everything. You have to actively go out of your way, making more work for yourself, to make it not support everything.
I don’t think you fully appreciate what goes into modern web design. Yes, web pages of plain text, formatted with <p> and <br> and maybe the occasional <img> to spice things up will work on all browser versions and is technically sufficient to convey text-based information. So, strictly speaking, it could be argued any page that departs from that is adding extra bells and whistles that restrict backward compatibility. However, that type of page bears as much resemblance to a modern site as a teepee does to a skyscraper. One can walk around New York City and decry all the pointlessly overcomplicated structures, but that doesn’t seem like it would be very useful.
The vast majority of web content producers and consumers value aesthetics and functionality over backward compatibility, so the language standards are going to evolve. One can dig in one’s heels on general principle, but you’re going to be the caveman wearing a bear pelt at a cocktail party.
The dude with the tall throat tells the truth. The new should accommodate the old, but only until it becomes an obstacle. A group of people ran science fiction conventions in my area and they had a website up that, to accommodate some older members, actually had to be compatible with whatever Commodore software the techno-fogies were using at the time, and this went on far longer than it should have. Try to imagine how threadbare a website has to be for that kind of backwards compatibility to work.
I went there to try it out. I could read it, but it wouldn’t let me post without registering. Not going to register just to try it out. Based on what I could see, though, my main impression is ugly, ugly, ugly.
Hilarious. There are whole aisles of books in your nerdier bookstores dedicated to the science, no, scratch that, the art, no scratch that, the voodoo of cross-browser compatibility. Yes, even for stuff that adheres to standards. There are highly paid developers whose entire reason for being valuable is that they know all the tricks. Most web developers don’t actually try to know all the arcane differences and just use compatibility layers like jquery to abstract away the ball-of-shit that is browser “standards” adherence (and stuff that differs simply because of the standards often not being specific enough). And IE6 is widely regarded as the most difficult to support in recent history.
Incorrect: many browsers are not standards-compliant to the current HTML standards (Acid2 - Wikipedia)
Also, I have yet to see a version of Lynx that supports HTML5.
On the off chance you’re serious, that website has terrible content and organization–rightly so, since it’s expressly the idiosyncratic expression of a bunch of neckbeards, but hardly anything to hold up as a shining beacon on a hill.
I wasn’t pointing to the content or organization, I was pointing to their use of minimalist HTML to display their content. No excess graphics, no backgrounds, just a plain background, plain text, and nothing that does not actually qualify as content. No unnecessary HTML, at that. If it doesn’t have to be there for the display of the content, it isn’t there.
BTW, though, I like their content. But I’m an idiosyncratic neckbeard, myself.
:p:p:p
I thought you were joking about that page.
Using"excess" and “unnecessary” html to provide organization, context and functionality is extremely important and valuable to the consumers of the information.
Maybe you can give examples of which html is “excess” and which is not?
But you are wrong - they have a stupid quote and an angry squirrel icon at the top.
If LYNX doesn’t do it as plain text, it’s excessive. Yes, I’m a Luddite. The Apple IIe was the highest form of “computer”.
Actually, it is. I share the opinion expressed by others that the demo is fugly. I don’t go into bars that look shady, or restaurants that look dirty. Aesthetics is an important part of the site experience. Fugly turns me off. I have better things to do with my time.
Yeah, this. Using a ‘fugly’ example may turn people off before they look at the underlying house. Use a clean layout, then tell people about all the shag carpet and marble countertops they can get as options.
Maybe he needs someone who can do layout and style and stuff, so he can manage the structure and tools and such.
Sorry for the bump, but I don’t feel like starting a new thread for this question. But how often is the vBulletin software updated here? This board is still on 3.7.3, but they have came out with 5 Connect.
I would say the last change would have been around 2007; 2008 if they evaluated it first.
Thing is: New Is Not Always Better; upgrading can break things bad; a lot of customization can be lost in an upgrade; and it costs for new licensing — vBull used to have licences for life if you paid for it; now it’s strictly annual. There’s no reason for them to waste money.
Plus as a bon-bouche the newer vBulletins are fugly.
I gave a talk about this, and Straight Dope is covered extensively. Some of the posts here are even highlighted in my talk!