Re: Browsers will never get it right [was Re:Blocked-base parsing?]

Orion Adrian schreef:
>>>>> So I say that a new model is already upon us. I say that it's time we
>> That's basically just describing the normal lifecycle of standards.  Start
>> with bloat; new lean and mean targetted; industry committees; new bloat.
> At some point, hopefully, a lesson is learned. Don't bloat. Stick with
> targetted specs. Not every company is making these mistakes.
> Ironically Google has learned to keep it's products lean and keep them
> lean. Ben Goodger of Firefox seemed to learn the lesson as well and
> understood that extensions were key.
Firefox is a new product. Who knows how bloated (or un-bloated) it will 
be in 10 years? That’s exactly what David meant to illustrate with the 
lifecycle - things are started anew to remove bloat (like Firefox was, 
and like Netscape 6 was before it) and in the end they become bloated 
again and something new wants to arise, and we’re back where we started. 
Firefox is just still early in its lifecycle, it is not a good 
counter-example at all.

Anyways, with regard to CSS, the goal is not a simple limited styling 
system for the web, but a comprehensive (yet still simple!) one which 
can be used in professional applications (such as for print), supporting 
different scripts and styling.  Especially in those areas, CSS3 adds a 
lot of value. CSS3 is not adding more bloat, it is just more progress in 
the grand whole which will ultimately be ‘CSS’.

And hopefully, at some point CSS will do all that is needed, and it will 
be ‘done’, only needing incidental small additions. Only if at that 
point things will still be added just for the sake of adding things, I 
think it can be called ‘bloat’. But that’s a matter of perception, I guess.


Ushiko-san! Kimi wa doushite, Ushiko-san!!
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: Backbase employee;

Received on Thursday, 15 September 2005 22:22:29 UTC