First off, learn to argue without resorting to derogatory name calling and thinking calling someone moron makes you superior, it doesn’t. Second, I was talking about Opera’s case, about what they should prioritize and what not. Keep that in mind and do not read between the lines.
Good job, you found some bullshit marketing crap from IE developers. I read those, not convinced that HWA is making my general browsing any better. In fact, DirectWrite seems to screw up the fonts,which is more irritating. Computers with older CPUs, as you put it, do not come paired with good GPUs, and older systems like that are not supported by HWA anyway. You’re trying to make a case situation that does not exist. Moreover, CPU to GPU and memory bandwidth in those older systems means HWA, even if it works, is just going to make things more laggy in ancient hardware because of the delay introduced by the new layer. I know about Chrome’s implementation because I run Chrome Canary, and just a few builds ago using GPU composition was making all the websites render incorrectly. Chrome’s HWA isn’t even remotely as fast as IE either, or even FF.
Extending features which nobody are using is only for froth-mouthing geeks to swoon over and compare like their e-peen of their browser of choice. The -webkit case is not an issue of browsers not supporting the features, because most of the browsers already do support those, and the websites that are using them are recent, not old from when only webkit had those features. It is an edge case of mobile web developers being too lazy and saying fuck-all to non-webkit browsers, mainly because they were designed to only work on iProducts. And that’s a part of CSS, not HTML5. A little knowledge is a dangerous thing, especially when foul-mouthed people like you try to use them for arguments they don’t have any clue about. And since we are in that region, it was BECAUSE Webkit started pushing non-standardized crap like that that we are in a situation like this. Most of HTML5 isn’t finalized either, and they don’t have the prefix issue, so you’re comparing Apples to Oranges. If a browser doesn’t support a specific HTML5 feature, it’ll simply not work. Yet I don’t see FF with its measly HTML5 score not working on a ton of sites. So, think again. You push non-finalized crap now in browsers. then all the websites start using it, and we end up in a situation where we have to support buggy unfinished specs becuse they are “too prolific by now”.
You’re using the days of IE6 as a juju to scare people into adopting unnecessary unfinished standards which do not contribute to user experience apart from a few edge cases affecting less than 1% users. Yet when I say that Opera should focus on fixing their position:fixed bug which makes several of the most visited websites frustratingly slowly, I’m wrong? Yeah, love how you’re using your logic. Or the lack thereof.
I’m not saying you do not ever need webGL or HWA, I’m saying Opera has better things to do first than these.