W3C home > Mailing lists > Public > www-style@w3.org > June 2007

Re: Stylings only possible with Tables

From: Raul Dias <raul@dias.com.br>
Date: Tue, 26 Jun 2007 09:00:56 -0300
To: Daniel Beardsmore <public@telcontar.net>
Cc: www-style@w3.org
Message-Id: <1182859256.5036.161.camel@speedy.swi>

On Tue, 2007-06-26 at 02:40 +0100, Daniel Beardsmore wrote:
> Spartanicus wrote:
> > about five years to be implemented ...
> Good grief. Either CSS is already in a far worse shape than I realised, or 
> you're severely over-estimating the complexity of basic layout. If it takes 
> *FIVE* years for people to write some simple layout code, then CSS needs 
> taking out, shooting and starting over.
> Five years ... I don't know if browsers have crap coders, or CSS is so 
> unwieldy that it will take that long to figure out how anyone is supposed to 
> build on it.

Consider that the CSS 2 specification was written 9 years ago and still not 
fully implemented on major browsers (the exception might be opera).

This is just what I think about it, not necessarily true.

Back in the MS vs Netscape War days, implementaion and development were
in a fast pace because of competition.  Who ever satisfied webdevelopers
needs first got the cut.  Which lead to a sea of propietary resources
which some came to a common ground later through standards.

So, back then standards play catch up with the browsers.  This fast
development had a cost,  Bad Code. NS 5 didnt take off and IE7 needed a
lot of rewriten too (AFAIK).

So, now the browsers are catching with standards.  Mozilla was written
from the ground up with standards in mind (a lot to catch up) an IE7
difference with IE6 is mostly about standads compliance.

The "problem" as I see, is that browsers now are waiting for standards
to dictate the rules, but standard pace is slow as it always was.  So
now that the browsers catched most of where the standards are,
developers are catching up too and the "holes" of the standards start to
become clear.

This is a good thing because allows the standards to walk in the path it
is really needed, it doesnt have to guess what developers would like to
have.  Developers are already crying at their door for what they need.

The "problem" is that by the slowliness to get things done, browsers
might start to go heavy again on proprietary stuff to solve developers
needs.  IE still have 70%+ of the market so still easy for MS to recover
ground and ditch the competition (I was already expecting this from
IE7).  Or easier to Mozilla and others to step up and get more ground.
If this happens, there will be a war again and standards will be playing
catch up again with browsers.

-Raul Dias
Received on Tuesday, 26 June 2007 12:02:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:29 UTC