- From: Samuel Ondrek <samuel@ondrek.com>
- Date: Tue, 19 May 2015 12:23:53 +0200
- To: Zack Weinberg <zackw@panix.com>
- Cc: Jens Oliver Meiert <jens@meiert.com>, W3C WWW Style <www-style@w3.org>
Ideal CSS would be no CSS.. We want to style the web with maximal efficiency and semantic, but keep easiness and accessibility for everyone who is new — as it was last 20 years. Every new property increases the learning curve (what is very bad), but also almost every new property makes the language more semantic and makes CSS a better tool for solving problems. In general I agree, radical simplification is not a solution — but neither a radical complexity. If CSS’ve grown from 53 to over 300 properties, the question is — does every one particular prop make the language better, or we are just too enthusiastic about the possibility that "we can” add the fanciness. > On 18 May 2015, at 17:52, Zack Weinberg <zackw@panix.com> wrote: > > I understand where you are coming from with this, but I believe that > everything I wrote at > https://www.owlfolio.org/research/radical-simplification-will-not-save-the-world/ > applies equally to this as to security. > > On Mon, May 18, 2015 at 10:53 AM, Jens Oliver Meiert <jens@meiert.com> wrote: >> A few concerns about the growth of CSS &c.: >> http://meiert.com/en/blog/20150518/fing-up-standards/. >> >> Personally I’ve been concerned about this for some time—from my view >> common HTML and CSS code gets worse by the hour, with problems >> typically being addressed by what caused them in the first place: new >> features. (This is a generalization, but you get my drift.) >> >> However, this is solely meant to keep the topic alive. >> >> (Also shared with two other groups, posted separately to honor group >> preferences.) >> >> -- >> Jens Oliver Meiert >> http://meiert.com/en/ >> >> ✎ The Little Book of HTML/CSS Frameworks: http://meiert.com/frameworks >> >
Received on Friday, 22 May 2015 12:43:52 UTC