Slashdot Mirror

← Back to Stories (view on slashdot.org)

CSS 2.1 Becomes W3C Recommendation

Posted by Soulskill on from the making-haste-slowly dept.

yuhong writes "After about a decade of development, CSS 2.1 has become a W3C recommendation. From the announcement: 'The current interoperability makes it easier than ever for developers and designers to enrich the toolkit. W3C expects future additions to CSS to be organized as independent modules, allowing smaller, more focused feature sets to progress and stabilize at their own pace. Some of these new features are already supported in browsers and other software in draft form (using the built-in CSS prefix mechanism designed for experimentation). As interoperability improves for each one, developers can transition to the standard to simplify their code. The CSS Working Group also publishes snapshots of which CSS features are supported interoperably in browsers; see, for instance, the most recent CSS Snapshot.'"

1 of 97 comments (clear)

  1. CoffeeScript is a bandage over a horrible wound. by Anonymous Coward · · Score: 0, Flamebait

    CoffeeScript isn't "good" in any way. It's merely a bandage over the horrible wound that is JavaScript.

    Every aspect of JavaScript is a failure. Every single one. They managed to fuck up the syntax. They managed to fuck up the semantics. They managed to fuck up prototype-based OO. They managed to fuck up the equality and inequality operators. The fact that you need to hide it as much as possible, whether using something like jQuery or CoffeeScript, further goes to show how anally fucked it is.

    JavaScript has no redeeming value. There's nothing good about it. Frankly, it should have been destroyed years ago. But browser developers haven't exactly shown themselves to be the brightest people around. I mean, just look at Firefox. Who the fuck thinks it's a "good idea" to write huge portions of a desktop app using JavaScript and XML? It's no wonder it is so fucking bloated, slow, and prone to memory leaks, and it's supposedly a "lightweight" browser.

    It's time for a real programming language in the browser. It doesn't matter if it's Lua, or Scheme, or Python, or Ruby, or Erlang, or even Haskell. We just need to get rid of JavaScript. We need to get rid of what is actually the biggest mistake ever made in the field of computing.