Monday, December 17th, 2007
Alex discusses the Opera case (how it is a bad idea), and how Opera could be more productive.
He calls out how we can’t hide behind the “let’s just make IE work with standards better” line:
In order for the future to be better by a large amount, it must be different by a large amount.
Until we get some great new (non-standard) CSS features out Mozilla, Opera, and IE nothing will get better to the extent that we will again be optimistic about the future (Safari earns a pass). The size of the improvements they deliver in the future are directly tied to our expectations of how different the future will be. Only when there are large and divergent ideas of how to proceed expressed through competing, successful implementations will standardization really work to whatever extent that it can reasonably be expected to.
Let that sink in a bit. To get a better future, not only do we need a return to â€œthe browser warsâ€, we need to applaud and use the hell out of â€œnon-standardâ€ features until such time as thereâ€™s a standard to cover equivalent functionality. Non-standard features are the future, and suggesting that they are somehow â€œbadâ€ is to work against your own self-interest.
Web developers everywhere need to start burning their standards advocacy literature and start telling their browser vendors to give them the new shiny. Do we want things to work the same everywhere? Of course, but weâ€™ve got plenty of proof to suggest that only healthy browser competition is going to get us there. Restructuring the CSS WG or expecting IE8 to be â€œfully standards compliantâ€ is a fools game.
*listens to a beating drum*
Posted by Dion Almaer at 8:32 am