Well you're right in saying HTML5 does not replace HTML4; and it was never meant to. It is simply an addition. Much like CSS3, CSS3 properties extend the library of already existing properties, in the same way HTML5 extends HTML4. It is not a new language and not meant to replace anything. More tags are added to provide easier, more efficient ways of doing things which are seen as common practise; to ease the changing of development needs as the internet evolves. HTML4 still exists so does HTML1.
I'm gonna pick out a few quotes to correct, discuss or reflect on:
Runawayhorses wrote:HTML4 is very much alive and recognized in all browsers and HTML5 does not appear to be taking over or offer anything noticeably better than 4 I will continue to ignore 5 and use 4
A lot of HTML1 is still very much alive too, many of the tags you see originated from it, but a lot of HTML1 is also dead and gone and will be ignored by browsers. You could write an entire website using only tags from HTML1, but you'd have to do a lot of repetitive work and will soon realise, HTML2 offers easier options ... and so on up the line.
But there is no such thing as "writing in HTML5", when you write HTML4, you are also writing HTML3, 2 and 1 at the same time. Making the jump to 5 is nothing. If you find a tag in HTML5 which you find useful and you use it, doesn't mean you've moved on and neglected HTML4 never to turn back... it still remains.
Mr.EasyBB wrote:The stability of it is outstanding
The stability depends on the browser. I imagine you mean "support" ?
Mr.EasyBB wrote:HTML4 can not withstand that.
Its not that HTML4 can't stand it. It's just browser versions written and released before HTML5 would not have included that tag in their parser. They could technically go back and add it...
Mr.EasyBB wrote:webkit driven devices
WebKit is the Chrome/Safari rendering engine. If its an old version, then it makes no differences. As explained above, if it was written before HTML5, then it won't include HTML5.
Runawayhorses wrote:Easier to write doesn't make it better
No, but often newly provided native browser methods and options are much more efficient.
Runawayhorses wrote:All still work, they have not depreciated.
Deprecated does not mean they will no longer work. Deprecated means they are no longer supported by the developers, will never be improved on and a much better alternative is available, additionally may be removed in the future. Deprecation, is to give developers a heads up to the potential removal of an item/feature - due to whatever reason most likely a more efficient, faster, secure and easier option has been created. The browser developers choose whether or not they want to remove deprecated tags. Mozilla might begin making a new Firefox browser tomorrow and say "Oh my, all these old HTML4 tags are taking way too much room, its time to go" and so their next version will not support them - they're old versions will however. Which is why keeping up with the times is very important, and deprecated items shouldn't be used. As they likely will
disappear in the future.
Runawayhorses wrote:I'm all for better ways of doing things and I think HTML5 is about that, but it simply is not going to replace HTML4, what its going to do and does is add functionality and ease of use to already existing HTML4. Its all HTML, just calling it 5 gives it a distinction that its new HTML code, they all work together because they are the same. All the browsers in the world will always continue to support HTML4 because its not being replaced, HTML is introducing more code, and they are calling HTML5.
Bang on the money, nail on the head, etc etc.
The difference between <input type="text" > and <input type="text"/> isn't HTML4 and 5. That's more displaying the difference between standard HTML (<input type="text" >) and well-formed HTML, known as XHTML (<input type="text"/>).
Tables should be used for tables
They actually take longer to render, which is why most phpbb2 forums appear sluggish.
Anyway, good discussion.