Martian Headsets - Joel on Software - The Diigo Meta page

• 03 Jul 09
  

  Graham Perrin

  Joel takes on the difficult issues of standards and vendor specific implementations. This is a classic!

  ODF Browser-Wars document-wars HTML+ WebKit unread 2009 Office Open XML

• 02 Jul 09
  

  Gary Edwards

  Joel takes on the difficult issues of standards and vendor specific implementations. This is a classic!

  ODF OOXML Browser-Wars document-wars HTML+ WebKit

• 30 Jun 09
  

  Paul Merrell

  web standards joel spolsky IE8

  • You’re about to see the mother of all flamewars on internet groups where web developers hang out. It’ll make the Battle of Stalingrad look like that time your sister-in-law stormed out of afternoon tea at your grandmother’s and wrapped the Mustang around a tree.
  • The flame war will revolve around the issue of something called “web standards.”
• 01 May 09
  

  Tim Jacob

  webdesign html

• 07 Aug 08
  

  Xavier Saint-Denis

  !check blog

• 11 Apr 08
  

  Wisely

  webdesign standards webstandards websites

  • If you’ve ever visited the ultra-orthodox Jewish communities of Jerusalem, all of whom agree in complete and utter adherence to every iota of Jewish law, you will discover that despite general agreement on what constitutes kosher food, that you will not find a rabbi from one ultra-orthodox community who is willing to eat at the home of a rabbi from a different ultra-orthodox community. And the web designers are discovering what the Jews of Mea Shearim have known for decades: just because you all agree to follow one book doesn’t ensure compatibility, because the laws are so complex and complicated and convoluted that it’s almost impossible to understand them all well enough to avoid traps and landmines, and you’re safer just asking for the fruit plate.
  • Standards are a great goal, of course, but before you become a standards fanatic you have to understand that due to the failings of human beings, standards are sometimes misinterpreted, sometimes confusing and even ambiguous.
  • 10 more annotations...
  • • A mortal web designer who attaches a DOCTYPE tag to their web page saying, “this is standard HTML,” is committing an act of hubris. There is no way they know that. All they are really saying is that the page was meant to be standard HTML. All they really know is that they tested it with IE, Firefox, maybe Opera and Safari, and it seems to work. Or, they copied the DOCTYPE tag out of a book and don’t know what it means.
    • And this is where Jon Postel caused a problem, back in 1981, when he coined the robustness principle: “Be conservative in what you do, be liberal in what you accept from others.” What he was trying to say was that the best way to make the protocols work robustly would be if everyone was very, very careful to conform to the specification, but they should be also be extremely forgiving when talking to partners that don’t conform exactly to the specification, as long as you can kind of figure out what they meant.
    • The victory of the idealists over the pragmatists at Microsoft, which I reported in 2004, directly explains why Vista is getting terrible reviews and selling poorly.

    • And so if you’re a developer on the IE 8 team, your first inclination is going to be to do exactly what has always worked in these kinds of SEQUENCE-MANY markets. You’re going to do a little protocol negotiation, and continue to emulate the old behavior for every site that doesn’t explicitly tell you that they expect the new behavior, so that all existing web pages continue to work, and you’re only going to have the nice new behavior for sites that put a little flag on the page saying, “Yo! I grok IE 8! Give me all the new IE 8 Goodness Please!”

      
      

      And indeed that was the first decision announced by the IE team on January 21st. The web browser would accommodate existing pages silently so that nobody had to change their web site by acting like the old, buggy IE7 that web developers hated.

      
      

      A pragmatic engineer would have to come to the conclusion that the IE team’s first decision was right. But the young idealist “standards” people went nuclear.

    • Almost every web site I visited with IE8 is broken in some way. Websites that use a lot of JavaScript are generally completely dead. A lot of pages simply have visual problems: things in the wrong place, popup menus that pop under, mysterious scrollbars in the middle. Some sites have more subtle problems: they look ok but as you go further you find that critical form won’t submit or leads to a blank page.

      
      

      These are not web pages with errors. They are usually websites which were carefully constructed to conform to web standards. But IE 6 and IE 7 didn’t really conform to the specs, so these sites have little hacks in them that say, “on Internet Explorer… move this thing 17 pixels to the right to compensate for IE’s bug.”

    • The consumer is not an idiot. She’s your wife. So stop laughing. 98% of the world will install IE8 and say, “It has bugs and I can’t see my sites.”
    • The web standards camp seems kind of Trotskyist. You’d think they’re the left wing, but if you happened to make a website that claims to conform to web standards but doesn’t, the idealists turn into Joe Arpaio, America’s Toughest Sheriff. “YOU MADE A MISTAKE AND YOUR WEBSITE SHOULD BREAK. I don’t care if 80% of your websites stop working. I’ll put you all in jail, where you will wear pink pajamas and eat 15 cent sandwiches and work on a chain gang. And I don’t care if the whole county is in jail. The law is the law.”
    • On the other hand, we have the pragmatic, touchy feely, warm and fuzzy engineering types. “Can’t we just default to IE7 mode? One line of code … Zip! Solved!”
    • Secretly? Here’s what I think is going to happen. The IE8 team going to tell everyone that IE8 will use web standards by default, and run a nice long beta during which they beg people to test their pages with IE8 and get them to work. And when they get closer to shipping, and only 32% of the web pages in the world render properly, they’ll say, “look guys, we’re really sorry, we really wanted IE8 standards mode to be the default, but we can’t ship a browser that doesn’t work,” and they’ll revert to the pragmatic decision. Or maybe they won’t, because the pragmatists at Microsoft have been out of power for a long time. In which case, IE is going to lose a lot of market share, which would please the idealists to no end, and probably won’t decrease Dean Hachamovitch’s big year-end bonus by one cent.
    • As usual, the idealists are 100% right in principle and, as usual, the pragmatists are right in practice. The flames will continue for years. This debate precisely splits the world in two. If you have a way to buy stock in Internet flame wars, now would be a good time to do that.
• 01 Apr 08
  

  Kathryn Frech

  IE web standards webdesign

• 21 Mar 08
  

  Egon Bianchet

  About realism and idealism on web standards — interesting info on backward compatibility, but a bit of confusion about document structure and rendering.

  ie webdesign webstandards

  • DOCTYPE is a myth.

    
    

    A mortal web designer who attaches a DOCTYPE tag to their web page saying, “this is standard HTML,” is committing an act of hubris. There is no way they know that. All they are really saying is that the page was meant to be standard HTML. All they really know is that they tested it with IE, Firefox, maybe Opera and Safari, and it seems to work. Or, they copied the DOCTYPE tag out of a book and don’t know what it means.

    
    

    In the real world where people are imperfect, you can’t have a standard with just a spec–you must have a super-strict reference implementation, and everybody has to test against the reference implementation. Otherwise you get 17 different “standards” and you might as well not have one at all.

• 

  Mikhail K

  2read api

• 19 Mar 08
  

  tony curzon price
  • If you’ve ever visited the ultra-orthodox Jewish communities of Jerusalem, all of whom agree in complete and utter adherence to every iota of Jewish law, you will discover that despite general agreement on what constitutes kosher food, that you will not find a rabbi from one ultra-orthodox community who is willing to eat at the home of a rabbi from a different ultra-orthodox community. And the web designers are discovering what the Jews of Mea Shearim have known for decades: just because you all agree to follow one book doesn’t ensure compatibility, because the laws are so complex and complicated and convoluted that it’s almost impossible to understand them all well enough to avoid traps and landmines, and you’re safer just asking for the fruit plate.
• 

  Ryan Baker-Smith

  Web.Design.General

• 18 Mar 08
  

  David r

  The flame war will revolve around the issue of something called “web standards.” I’ll let Dean introduce the problem:
  
  All browsers have a “Standards” mode, call it “Standards mode,” and use it to offer a browser’s best implementatio

  standards

• 

  Ian Usher

  browser ie8 microsoft standards toread web webstandards

• 

  venomino

  webdesign

• 

  Francisco Javier Alcala-Soler
• 

  Moultrie Creek

  Discusses the issues of IE8 supporting web standards.

  standards webdesign

• 

  takayuki kawamoto

  arc standards ie8 web webstandards browser microsoft

• 17 Mar 08
  

  Stephen Carr

  for:kelv article webdesign web webstandards

• 

  Isaac Pigott

  standards toread webstandards occam browser ie8 microsoft delicious

• 

  Marc Ordinas i Llopis

  "every working software developer should understand, at least, how standards work, how standards should work, how we got into this mess" Joel on web standards.

  web programming development

• 

  Frank Colcord

  Ruby

• 

  Elijah Lofgren

  web browser webstandards standards toread software css html

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.