8 ms·
What’s Wrong with “HTML5″
- mechanical_fish 16y agoWe need to hope that Tim O'Reilly can invent a better term. I'm quite serious. "Web 2.0" may have been an amorphously defined grab-bag of a concept, and some people didn't like it, but at least it didn't get itself confused with a W3C standards document. If you call something "Web 2.0 compliant" people tend to recognize that you are kidding.
- ceejayoz 16y agoMost of the people I've heard say "Web 2.0 compliant" aren't kidding.
- mechanical_fish 16y agoWhen composing my original sentence, I chose the word tend very carefully. ;)
- terra_t 16y agoI think it's harmless, and it crystalizes the idea that things are changing, the same way that the term "Web 2.0" did. Muggles have a lot of trouble with names. I worked for a big Uni back in the age when Mozilla's browser was caled "Mozilla" and it was impossible to get anybody to take Mozilla seriously. This was a place full of Unix-heads and Microsoft-haters, and we found that in 2002 we still had a 30% market share on campus of the despicable Netscape 4 browser. When "Firefox" came out, all of a sudden the muggles realized there was an alternative to IE, so Netscape 4 finally died for us. The project to obliterate flash and replace it with something open needs a name... And "HTML 5" is as good as any, inprecise as it is.
- knowtheory 16y agoYehuda's point is actually that HTML5 is NOT like Web2.0. Everybody knew that Web2.0 wasn't a thing. Now there are people confusing HTML5 as a thing with the process of making the web better.
- catshirt 16y agoperhaps i'm living in blissful ignorance, but who?
- terra_t 16y agoPeople regularly convert verbs into nouns. It's a semantic error, but it makes the invisible process of "making the web better" visible to the muggles.
- Qz 16y agoIt's not an error, it's a feature! In all seriousness.
- knowtheory 16y agoverbing nouns does indeed weird language, but that's not the point here. The point that analysis of HTML5 as a standard is not the point of the current effort to improve the web, and improve computing in general. It does not matter where HTML5 and Flash happen to stand at the moment in aggregate usage across companies. Who cares. There are many reasons for adoption of each technology, dependent on the circumstance of each company and their business models. That's why HTML5 as a noun is a bad banner, avatar, symbol, whatever. Web2.0, nebulous as it may have been, could not be confused with an actual object. HTML5 suffers the same problem that XML did. People thought anything that touched XML was going to be the wave of the future, and improve everyone's lives, and be both machine and human readable, and lead to a revolution in how metadata was transported. It is true that XML lead to cool new capabilities on the web. It also was not a panacea, nor did it instantly make any project that used it awesome (XML config files are one of the most heinous digital inventions ever). People should not confuse the movement to create better web technologies, with the web technologies themselves, or we will all miss the point.
- kreek 16y ago"The project to obliterate flash and replace it with something open needs a name..." How about 'Throwing a perfectly good technology out with the bath water in the name of open source zealotry so that we can replace it with a mish-mash of SVG and Canvas graphics, multiple non DRM video codecs, and an ever moving WebSocket spec'? :) Let the down votes begin!
- terra_t 16y agoNote that Microsoft and Apple want to obliterate flash just as much as anybody does... IE9 shows that even Microsoft realizes that "HTML5" is a far deadlier weapon than Silverlight.
- kreek 16y agoActually if the rumor from the front page is correct Microsoft want to buy Flash (and the rest of Adobe).
- wingo 16y agoI'm really amused that you called them muggles, and that everyone knows what you mean :)
- olalonde 16y agoI genuinely don't get the author's arguments. Unfortunately, the term, and therefore the way the technology is understood by tech writers, is causing some fairly serious problems. The thing is, the core problem isn’t that the name is too fuzzy. It’s what the name implies. The truth is, the “completion” of HTML5 is absolutely irrelevant. Basically, the tech press shouldn't use the term HTML5 because they don't understand it? HTML5 is a major milestone for the web and the term carries much more meaning than previous buzzwords (AJAX, Web 2.0, DHTML, etc.). HTML5 is a new technology unlike AJAX or DHTML which defined new ways of using existing technologies (AJAX = Javascript + XMLHttpRequest API, DHTML = HTML + Javascript DOM manipulation). Unlike those terms, HTML5 is very well defined and therefore quite hard to misuse. Am I missing something?
- daleharvey 16y agoyour confusion is exactly what the article was about html5 is not a milestone, its a progression, it will never be finished and it started a long long time ago.
- kenjackson 16y agoI must admit, I'm confused. I will never be finished? Isn't it just a specification? Isn't there some time when they say the spec is done and signed off on by the appropriate standards bodies?
- steveklabnik 16y agoActually, after the first version of the spec is finalized... html will be versionless. Hence `<!doctype html>`.
- olalonde 16y agoI wasn't aware of that. Won't it be living hell for web developers trying to build cross-browser compatible websites? Will you have to perpetually keep track of the implementation status of every HTML5 features for every browser in addition to keeping track of every browser version and their market share? Edit: I wasn't referring to the DOCTYPE. I was referring to the fact that up until now you could just assume it was safe to use HTML 4.01 because you knew it was implemented (almost) consistently across a large share of browsers out there. Now you will have to keep track of features individually instead of keeping track of a discrete set of features AKA a HTML version.
- msie 16y agoWell, I think it's too bad that HTML5 can't be treated like a milestone. Worrying about what will be officially recommended, what is or isn't part of HTML5 (geolocation API apparently) really puts me off thinking about developing for it.
- wycats 16y agoYou should be worried about what features have enough browser adoption in your target market to enable their use, not whether the W3C has marked a large group of loosely related technologies "done".
- rryyan 16y agoIt sounds like we need a nice, harmless, amorphous name like "Web 2.0" that the press can use to describe the new wave of next-generation websites. How about: "Web 3.0"
- nkassis 16y agoI think HTML Xtreme would do fine.
- robotron 16y agoI agree, "HTML5" is a stupid name for what it's being used for... but what is the tech press supposed to call the loose bundle of browser technologies? They're going to call it something chosen by the path of least resistance.
- adam_albrecht 16y agoI actually think it's great that the term has caught on. If people were to talk about "next update to the W3C standard" or about the features individually, it wouldn't be getting nearly as much press as it does. And with the increased press comes increased pressure on the browsers (I'm looking at you, IE!) to actually support the new standards.