Looking for HTML5 Nirvana
copperykeenclaws.com
copperykeenclaws.com
If anything, all the author expresses is the disappointment of his own expectations while not adding anything constructive.
Looking at the screenshots what he wants to achieve is perfectly doable cross browser but as per the author admission he's not much of a front-end guy.
Shots point to here > http://bigmath.herokuapp.com/ which is offline.
But yep, I agree - the author shouldn't necessarily try to start a debate without offering specific use cases and failures. Far too much conjecture IMO.
I had a similar thought like the author recently. Flash could have been awesome with a smaller runtime, 3D sooner, progressive rendering of content (text and images getting loaded in like in the browser instead of loading bars) Who would still use HTML? There would be no upside at all, Flash has always had better tools.
I have no problems centering content horizontally cross browser (which he complains about).
The authors example is terrible, that is an easy layout to do crossbrowser, HTML and CSS do have massive deficiencies in easily creating layouts, but so do most GUI toolkits, and compared to the other factors involved in the success of the web, fiddling around with css a little longer is a price well worth paying, for the majority at least
However, those deficiencies you mentioned are only "well worth it" because it's our only option. It's this complacent attitude that helped generate a need for a plug-in. HTML and CSS are still tedious to use and often times requires hacks to work in specific browsers. Why? We shouldn't need a mess of frameworks on top of frameworks to fix these "massive deficiencies", it's simply not good enough.
Latest Firefox, Opera, Safari, Chrome and IE10 - the bunch that supports both HTML5 and CSS3 from the start - are totally painless. That's the "HTML5 nirvana", IMHO. To be honest, breaking the compatibility between these the way the author did is quite an achievement - I really would like to see his code. Probably a quick and simple CSS Reset would solve these issues. Author's mistake is more probable though.
Old IE fixes a slight dirty, BUT can't get more basic HTML / CSS then this.
(Train delayed, Killing Time, Rainbows, etc.)
HTH Author.
No upside at all? Open standards, semantic code, SEO optimization, separation of presentation and content, ability to look into the source code, ability to alter the content and/or visuals by user, better printing support, userscripts, ad blocking,... Just to mention a few.
Anyway, no matter how good Flash could have become it would always be only a plug-in. A third-party injection, not an integral part of the web - and as such it always was doomed in the long term perspective. Relaying on plugins is like - excuse an over-the-top metaphor - having nitro system in a family car. It's exciting for a while, but nowhere near an experience of having a real supercar. HTML5, in it's current state, is not yet a Ferrari but it has way bigger chance to become one than Flash (or Silverlight, or anything) ever had.
There is a need for crazy, highly interactive studio/movie sites, webcam support on the web, cross-browser reliability, fast drawing for animation and games, cross-browser 3D, audio API. Saying that these features will come one day is not an answer. "You don't need those features because..." is also not an answer. The OP's points are no more constructive that those who have answers like these against Flash.
Criticizing HTML5 means you are pro-Flash. Which means you are wrong and all of your points are invalid. Even if you're not pro-Flash.
The problem is, the author hasn't backed up anything. There's no real valid criticism other than conjecture.
Dissent is the highest form of patriotism. Not offering criticism isn't supportive, it's religious. Being willfully blind to huge holes in necessary support won't make HTML5 better.
> The problem is, the author hasn't backed up anything.
It's not a research paper for a scientific discovery. It's an opinion on the state of HTML5. The OP doesn't need to back it up since proof of his points are rampantly apparent and readily available, cognitive dissonance excluded.
If you want HTML5 to get better, you should ask that it is better. Turning a blind eye is just foolish.
The exercise was a little more than straight-up horizontal centering. It was to take two numbers randomly generated with possibly different number of digits, center them together along with an operator as a block, but right-align the text within. Also a text input field was put below. The line above the input field is just a simple border.
For reference, the CSS tutorial I looked at was http://www.noobcube.com/tutorials/html-css/horizontal-and-ve..., but I didn't add the IE elements because I thought it was only necessary for IE 6 and 7, not 9.
So the horizonal alignment problem in IE is probably because I used display:block. But why don't the numbers line up the same in chrome and firefox? What's up with the field border being all over the place? My point is not that I know html and css well, which I clearly don't, or that this stuff is impossible. It's that even with the latest browsers and techniques, it's still easy to get very different displays. I just didn't expect that, given the huge hype surrounding html5 and css3.
Without seeing your code it's hard to tell what exactly gone wrong, however such huge level of browser inconsistency is indeed worrisome. Never believed HTML5 would solve these kind of issues completely but the differences shouldn't be that huge.
Can you please share markup/css you were using?
Well, as the HTML5 specification is not complete yet... the answer is quite obvious: No.