41–50 of 131 posts
Sensationalist link-bait headlines have no place here IMHO.
59 points and (at the time of writing) top post would indicate some disagree
Literally the only problem with CSS itself is that it doesn't have defines. Every other problem is just browser implementations.
CSS has very weak layout capabilities.
CSS has weak typography.
CSS has weak colour system support.
In each case, this is partly due to limitations in the underlying model, but also partly due to having limited syntax.
In each case CSS3 modules may improve things somewhat if and when they are widely supported, but even the best proposals there aren't even close to the power of a good DTP tool or the control of a native application. When the web is trying to take over from both, CSS isn't a good tool, it's just the best we've got right now.
Obsolete isn't a verb.
Says who? http://www.merriam-webster.com/dictionary/obsoleted http://en.wiktionary.org/wiki/obsolete
It's an opinion, take it with a grain of salt.
(BTW, I dislike MW because it takes all nuance out of the language and dumbs it down to an inexpressive mess.)
Earlier quoted context omitted.
Says who? http://www.merriam-webster.com/dictionary/obsoleted http://en.wiktionary.org/wiki/obsolete
Obsolete is a verb, but it is a poor choice. A better choice would be obsolesce, as in: "LESS.js will obsolesce CSS". This is because LESS.js won't obsolete CSS, but it may well start the industry on the path. Obsolete has a feeling of immediacy to it, and obsolesce has a feeling of lethargy or a gradual process which is why it's the better choice. It's an opinion, take it with a grain of salt. (BTW, I dislike MW bec…
Def initely
Literally the only problem with CSS itself is that it doesn't have defines. Every other problem is just browser implementations.
Earlier quoted context omitted.
There is genuinely a tiny benefit because you don't need to declare colors etc more than once, everything else about it is trying to wedge ideas from other areas of programming into a language that contains so many abstract concepts as to not benefit from it at all. I've worked as a UI developer for 12 years now and I wouldn't go near something like this because there is no value. At least the server side version you…
Let me give an example use case, something I've wanted. Lots of developers will tell you that it's fine to use systems like the 960 Grid System for rapid prototyping, but you shouldn't use them for final, "production" sites. Their argument is that "littering" your code with classes like "grid_4", etc. is not semantic (and they're right). So here's what I would love to do: use a system like 960 in development, but ins…
.class-name .clearfix font-size: 1.2em
There are other ways to do it like one long string of selectors followed by the clearfix code, but they're not as convenient or readable.
Having said that, I have the same problem with LESS.js that I have with various other JavaScript layout techniques - I simply don't like relying on JavaScript to control the look and feel of a web page. I think it's awkward, inefficient, and just asking for trouble. Mostly, I also think it's completely unnecessary.
Obsolete isn't a verb.
Says who? http://www.merriam-webster.com/dictionary/obsoleted http://en.wiktionary.org/wiki/obsolete
If you take a gander at WordNet or even OneLook (searches multiple dictionaries), you'll find that the majority list obsolete only as an adjective, including Webster's 1828.
However, I concur that obsolesce would have been a better choice.