HTML6 Concept
html6spec.com
HTML6 Concept
1–10 of 89 posts
Re: HTML6 Concept
#2Re: HTML6 Concept
#3Re: HTML6 Concept
#4What's wrong with just using , and instead of , etc...?
Bad proposal IMO.
Re: HTML6 Concept
#5Which is fine. We have JSON and XML for data. I would rather see some cohesive standards for JSON data formats, because that is the future. HTML is just the glue between CSS and Ajax requests.
Re: HTML6 Concept
#6HTML5 did some very important things. Mainly it wrestled back the web from plugins.
Hey, remember Flash?
Isn't that great! That in 2014 I can say "Remember Flash?" Flash had such an insane grip on the web and now it's nearly gone! Not nearly, you might argue, but there are extremely few serious pages left that depend on flash. We've come a huge way since 2009.
It's crazy to think back, honestly. I'm amazed at how the grip of flash has receded. I would not have guessed in 2008 that this was where we'd be. I am a happy web developer.
This just doesn't solve the same scope of problems. It might be useful to some people, just like XHTML, but it's not worth building a new buzzword paradigm over.
[1] Everyone who writes a post like this deserves to be commended. Putting your own opinions out there is hard, so kudos to the author.
Re: HTML6 Concept
#7Funnily enough, at a first glance it looked like a real proposal, then I looked again and it appeared as a joke (I mean ... and are a bit satirical), and then I looked the repo and there's enough issues to think that it is actually real.
Re: HTML6 Concept
#8My first reaction is that I quite like it. It's more semantic than dozens of nested divs and spans, and perhaps that's not as useful for machine generated code - for those of us coding html by hand.
Re: HTML6 Concept
#9I simply can't imagine anyone wanting to adopt this. It seems like a lot of effort was put into the concept, and there are some great suggestions, but the added bloat goes against adopting the proposed solution.