- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Thu, 19 Jan 2012 00:50:51 +0000
- To: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
- CC: "www-style@w3.org" <www-style@w3.org>
[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.
Received on Thursday, 19 January 2012 00:51:34 UTC