Frequently Asked Questions (FAQ) about the future of XHTML

Finally! Bye bye!

The age of HTML5 finally coming... lol

I can imagine the hype when everybody starting to emphasize on HTML5

To most people, the change wouldn't even matter, and it'll probably take another 5-10 years before websites start using it properly. We haven't even properly migrated from broken html/xhtml yet

problem is, company is not moving away from ie6.

people is making noise on video and audio tag.

which is really sad......

this is true..same with css2

what is XHTML?

what is HTML 5?

see http://en.wikipedia.org/wiki/XHTML and http://en.wikipedia.org/wiki/HTML_5




XHTML 2 might be dead before it was born.. but XHTML 5 is the future.

you might need to change your post title. put something like "HTML is dead. they just call XHTML as HTML now."

This post has been edited by badai: Jul 15 2009, 04:30 AM

What practical advantage is there to XHTML over HTML? Will the majority of the developers actually need the XML serialisation of HTML5?

xhtml will die? surely, but not in our lifetime..

---

Added on August 6, 2009, 3:56 pmneed understanding? check this out :
http://www.smashingmagazine.com/2009/07/29...-2-comic-strip/

This post has been edited by simpul: Aug 6 2009, 03:56 PM

1. mr silverhawk is correct, it takes at least 5 years for people to properly use it

and the most important point is...

2. TMNuthouse Screamyx is holding HTML 5 out of people's reach, even if people are ready to deploy HTML 5 with streaming content to the web...

you like banging your mouse on the table, yelling 'FUUUUUUUUUUUUUUUUUUUUU-' while browsing HTML 5 streaming video? or you would rather stick with you tube like xhtml content?

Edit: yes, i'm bragging about the unlimited lagging speed of TMNuthouse Screamyx

This post has been edited by Instant_noodle: Aug 6 2009, 05:36 PM

I just like it because it has really simple rules and its strict. if we had strict rules for html from the start, it would have solved a lot of problems we have today.

edit: sorry, didnt notice that i am posting the same link as simpul

This post has been edited by jumanjisama: Aug 6 2009, 08:11 PM

I'm curious. For those who prefer XHTML, have you ever experienced or seen the "Yellow Screen of Death" while writing your XHTML? Is it a daily annoyance? Have you spent effort in avoiding it? Or are you wondering what is this "Yellow Screen of Death"?


... what are you going on about? >_>

Both HTML5 video and YouTube uses the same basic mechanisms. It's like complaining the JKR will cause Toyota cars to travel slower than Proton cars because JKR sucks - it doesn't make sense, the roads are the same for both.

That only happens if your xhtml is malformed.

Good analogy of JKR, Toyota and Protons. I agree that the wrong blame is put to Streamyx.

But the HTML5 video and Youtube's video uses totally different mechanism. HTML5 videos do not require any plugin to work, but YouTube's videos use Flash as the video playback engine.

And XHTML is not dead. XHTML 2.0 is dead (probably only for now). XHTML 1.x is still in maintenance.

blaming JKR? why bother when Toyota with less power can outrun proton by a mile...

"aiya... our line is better than congo ma... see, speed fast fast~~ if compared to them!!!", pff... you just don't know how many mouse i had 'killed' by banging onto table due to the lags from our 'fast fast connection'...

attempt to embed <video> or <music> tag in the future when HTML 5 finally made official? i think most people here will stick to embedded flash players, because streaming 4mb of flv/15mb of mp4 is less hassle.

-----------------------------------------------------------------------------------------------------------------------------------

during the introduction of Ajax VS Studio 2005, many people (whose stuck with IE6) had complained such technology has compatibility problem with their browsers and most of these problems are due to the fact that MS had fooked up some W3C standards. "We focus more on how it should run without flaws, rather than focus on other stuff" and this kind of response let me suffered occasional hangs from IE8 while FFx and Iron (chrome) cruising along (i run multiple browsers occassionally)

XHTML will still be the main stream, despite the 'excitement' that HTML 5 would brought upon the end user due to compatibility issues that plague IE users

If I didn't get you wrongly, I think you mean by using HTML5's embedded video, we are not streaming? What makes u think we are not streaming. You should try it. It IS streaming. It doesn't put the whole webpage on hold while loading the video. So the issue with the connection does not exist because if your connection can stream FLVs, it should be able to stream HTML5 videos without problems. The only prerequisite is the browser support.

EDIT: now I get what everling means when saying 'same mechanism'. So you were referring to the streaming nature?

This post has been edited by golvin: Aug 7 2009, 04:44 PM

golvin, yes. Although maybe I shouldn't have used Toyota and Proton. Perhaps Toyota and Honda?

Instant_noodle, HTML5 video playback is exactly the same as YouTube with only one major difference. You do not need Flash because the decoder is built-in.

This also allows the browser developers to treat the <video> as a first class citizen. Flash <object>s are notorious for hating CSS and other stuff that tries to overlay on top of it.

so, what we are actually trying to say is we are perfecting one thing which will never be perfect, the html itself.. for crying out loud, it is just a markup language.. if we wanted to perfected the language, we must change the minds of users who still uses older browsers and browsers which not support.. as for w3c concerns, what they do is a universal type thing, and thank to them for doing this..

+1

I've remembered spending most of my time arguing about technologies with my senior team lead but ended up delivering nothing. So it's kind of a red herring tragedy for me (lesson learned). But, when somebody start mentioning about supporting IE6, I'll start b****ing. For all web developer out there, start using http://ie6update.com/

This post has been edited by sunsuron: Aug 7 2009, 06:44 PM

check your stats, if many user use IE6, still have to support. not 100% must look like gecko & webkit browser. So so only ma.

Mostly we have to deal with CSS positioning like clearing float, double margin. ... but it is fakkap when the debugging time take too long.
I hope 2010 with less ie6 user & i will stop supporting it.

GO HTML5

edit :

add ie.css



This post has been edited by masahito: Aug 8 2009, 12:14 AM