Comments on: An epitaph for the Web standard, XHTML 2
Although the failed effort may have been a work of "philosophical purity," it was overshadowed by HTML 5. Why are Web standards so darned hard to create?
Although the failed effort may have been a work of "philosophical purity," it was overshadowed by HTML 5. Why are Web standards so darned hard to create?
Say No to boxed software! The future of applications is online delivery and access. Software is passé. Webware is the new way to get things done.
Add this feed to your online news reader
Don't buy these one-trick ponies--unless you like gizmos that gather dust.
The Net giant, ever eager for a faster Internet, debuts its Google Public DNS service. With it, Google could become even more central to the Net.
The communities needs shift, and adapt, making standards fluid over time, and self replacing by the actions of what the community uses, and needs most. There is an inherent life-cycle in that. Treating this process as a long term marketing opportunity to push a given product, or set of products fails in this scenario and will always have a great deal of resistance because they don't fit. Products fit "at the time", not always. Approaches work in very much the same way.
W3C could change its approach by studying the current trends and offering a good reference for others to implement.
This my friend is the type of world Microsoft has wrought upon every web user and most really don't realize it.
We are not so far advanced from the 19th century that we don't need standards.
A lot of people from the standards camp are also strongly in support of "free speech" and open source software. Well does it not make sense that Microsoft (or any other company/person) should be allowed to give their opinion on what they should support, and in essence support what they believe to be the future's direction?
For those people who say that IE was made solely to destroy Netscape and then to be let rot, well here's two facts you should know:
1. The plan for Microsoft's Internet embracement was completed before Netscape Communications (or even Mosaic Communications) existed as a company. This included plans for a bundled Explorer application. This also came as a result of IBM's resolution to bundle WebExplorer with their new OS. All this happened before Netscape existed. The public simply didn't know, because this was information that detailed Microsoft's plan. Of course, it's been a long time since then, so now we know.
2. Netscape was the one who wished to destroy Microsoft. Netscape was also the one who did not support standards. Of course, "standards" really weren't in place because the Internet was evolving too quickly. After the intense competition ensued, Microsoft came out as the winner, and not simply because they bundled Internet Explorer. Originally, NetScape was intended to be Windows 95's "killer app", but the guys at Netscape refused to work with Microsoft, and possibly even intentionally setting up a meeting such that the Department of Justice would try to stop Microsoft from bundling IE (we still don't know whether it was intentional or not). When IE was declared to be completely free (as in beer) for all platforms, Microsoft made a huge pledge to the world. The truth is, Microsoft had to pay ROYALTIES for each copy of IE distributed to a company called Spyglass, which Microsoft had licensed code from the Mosaic Viewer from, excluding copies distributed on Windows 95 and NT. This meant that they would have to pay extraordinary amounts of money to keep IE on other platforms, and because it was free, they could derive no possible benefit to shareholders, which obviously means something will have to be done...
In fact it has always been possible to make XHTML 1 pages which are backwards compatible, which work perfectly well event with browsers like Internet Explorer which do not support XHTML per se. The W3C, which creates the standards, defines clearly how this may be done, and I have been making such pages since the XHTML 1 specification first appeared.
Lack of backwards compatibility can therefore not be cited as a reason for XHTML's failure to become popular. A more compelling reason is that XHTML offers few advantages over HTML.
http://diveintomark.org/archives/2003/01/13/semantic_obsolescence
Standards should codify and tighten existing practice, not seek to invent new technology, as standards committees are just about the worst possible mechanism for doing so.
HA! Microsoft now cares about standards? This is a new development!
.Standards are standards and are designed to make a conforming Intenet, when the Internet is constantly evolving. It's only through evoloution that the Web became what it is now, a rich and living thing. XHTML works, but so does AJAX. There will always be evolving thoughts on the Web and people willuse different methods to meet their needs.
Standards don't work. Rather, a statement that the Internet is evolving at all times, and suggestions are always welcome and wanted, is what is needed. Who knows what someone will think up and make work tomorrow? Nothing is static and should never be static. Only through evolution will the net continue on. If there's only one way, be it HTML, XHTML, AJAX or some new way, then evolution is stifiled. Imagine if that happened to the rich world we live in now. Would we all continue to be protozoa?
What happened in the rich soup initially has evolved into what it is today. And one thing that just cannot be stopped is evolution.
</snark>
I'll take Flex or Silverlight over this rubbish any day.
- by sroussey August 8, 2009 12:11 PM PDT
- With Google's acquisition of On2, perhaps they will open source VP6 to everyone. "On2's VP3 codec is the actual basis for Ogg Theora. In 2001, On2 open sourced VP3 under an irrevocable free license through an agreement with The Xiph.org Foundation." Perhaps it is time again...
- Like this Reply to this comment
-
(20 Comments)http://www.theregister.co.uk/2009/08/06/google_vp6_open_source/