RE: The CSS Problem

>>>> http://meiert.com/en/blog/20121112/the-css-problem/
>>> You don't suggest an alternative.
>> I believe I do, by suggesting [...] more focus on the community.
> The adage that 80% of your users use only 20% of your features comes to 
> mind, as does the equally important adage that they all use a different 
> 20% of them.
I'm not an insider, but I think the situation in which the group is now is in most part due to the fact the CSSWG has two very different tasks to pursue: - Constantly innovate and solve the new authors' problems- Refine and make interoperable newly introduced tools As the usage of CSS surged in many different domains, so did the amount of problems the authors face. At this time, the only way for authors to get their problems solved is to ask the WG to work on it; as a result, there's an explosion of work for the WG, and dividing the group in focus group will certainly not help to reduce that task list. I think the best solution to the "work overflow" situation is to increase the workforce by allowing the community to create "forward polyfills" for CSS aka JavaScript shims that solve their needs in a sufficiently optimized way. After that, the CSS WG could work as usual by prioritizing the problems by usage and build standardized native solutions for them (useful to get performance increase, bug reduction and improved ease of use).  That means authors would have a "quick and dirty" way of innovating and solving their problems while the WG can keep a working pace allowing him to make beautiful and elegant decisions that will last forever. More on that soon.