HTML V5 and XHTML V2
An anonymous reader writes "While the intention of both HTML V5 and XHTML V2 is to improve on the existing versions, the approaches chosen by the developers to make those improvements are very different. With differing philosophies come distinct results. For the first time in many years, the direction of upcoming browser versions is uncertain. This article uncovers the bigger picture behind the details of these two standards."
Is Microsoft involved in this at all? If it is, then I am worried. Other than that, I can only say..."bring it on." It will be a matter of some kind of plug-in to make all viable browsers feel at home in whatever environment they find themselves in.
nobody cares about new web standards anymore.
I have to agree with Linus on this one.
His position on the matter is right on as always.
So I guess the question is which one Microsoft will ignore the most?
So if you are a developer and not a designer, why do you think you are qualified to even talk about how we should design our HTML or what browsers we should target?
Stop being so damn myopic and think like a designer or even *gasp* a business person. You are telling people that they should sign up to your religion, even if it means cutting off 70% of their market share. If you stood even an inch outside your "web developer" click and looked at the big picture, you'd see how insane you sound.
But yeah yeah yeah. IHBT and I'll HAND, thanks.
You may love the latest stuff shipping with Vista, but it's not on my computer and I'm not going to swipe a copy.
I don't even have Comic Sans, Ariel, Verdana, Times New Roman, etc.
I do have fonts. Some of them look kind of nice. You probably don't have them.
I often wish for an Open Source browser brave enough to say "screw the W3C, we're going to be IE compatible". I suppose it's OK to leave out the exploitable buffer overflows. I want the rest though.
...and so on, etc., ...
Recognize the popular ActiveX controls, providing Open Source substitutes when possible. Feed any remaining ActiveX crap into Wine, with appropriate sandboxing.
Do the VBscript stuff.
Do the DirectAnimation stuff.
Ignore MIME types; they get lost anyway when you save the files.
Being "right" just isn't worth the trouble. This isn't a fight worth fighting.