RE: @import -- allow at any place in stylesheet.

[Marat Tanalin:] 
> 19.01.2012, 04:50, "Sylvain Galineau" <sylvaing@microsoft.com>:
> > [Marat Tanalin:]
> >
> >>  18.01.2012, 21:58, "Sylvain Galineau" <sylvaing@microsoft.com>:
> >>>  [Marat Tanalin:]
> >>>>   18.01.2012, 21:16, "Sylvain Galineau" <sylvaing@microsoft.com>:
> >>>>>   [Marat Tanalin:]
> >>>>>>    18.01.2012, 20:48, "Ian Hickson" <ian@hixie.ch>:
> >>>>>>>    On Wed, 18 Jan 2012, Marat Tanalin | tanalin.com wrote:
> >>>>>>>>     In case of it was not clear enough yet: my goal is not to
> >>>>>>>> find
> >>>>>>>>  a
> >>>>>>>>     solution for a specific task. Instead, my goal is to
> >>>>>>>> improve
> >>>>>>>>  CSS
> >>>>>>    itself.
> >>>>>>>    Changes that aren't solutions to specific tasks aren't
> >>  improvements.
> >>>>>>    Consider increased flexibility as a task if you want.
> >>>>>   It's not. What the increased flexibility is used for would be
> >>>>> the
> >>  task.
> >>>>   Insreased flexibity, oddly to say, allows to increase usability,
> >>>>   productivity, and maintainability.
> >>>  Then provide one or more real-world example demonstrating all this
> >>>  will happen and explain why. General assertions are insufficient.
> >>  See http://lists.w3.org/Archives/Public/www-style/2012Jan/0760.html
> >
> > That is not a use-case. A use-case states a problem and explains how
> > the proposal leads to a better solution.
> >
> > That post simply says "If I have this feature I can X this way". It's
> > totally unclear why doing this way is superior or beneficial.
> 
> Do you understand what is flexibility? It's ability to do same thing
> different ways.
Do you understand why repeating the same word for the 15th time will not 
get you any further than it did the first 14? You assume 'flexibility'
is always inherently good, which is simply not true. If it can result 
in additional ambiguity and makes it far easier for authors to end up 
with circular dependencies between stylesheets and thus more bugs, in 
other words if, on balance, the costs may outweigh the benefits, then
it's not that worthwhile. 

Or it may be that there is some value to it; but there are far more
valuable things to spend our time on. When it comes to flexibility for
authors I'd rather spend time designing and implementing Variables. That
will give you and everyone else far more 'flexibility' for many years
to come.

The burden is on you to explain *how* and *why* this particular increase in
flexibility is beneficial. Or you can keep repeating 'flexibility' until
everyone ignores you.

Received on Thursday, 19 January 2012 15:38:16 UTC