Over the past 2-3 years, CSS has become the least bad part of the web, occasionally being actually quite pleasant. This makes it a bit painful for me to watch JS people try to 'fix' the least broken part of the web by breaking it just enough for it to be familiar to them.


@baldur I respectfully disagree. After studying the 2.1 spec I have found it to be the most confusing hodgepodge of concepts that are layered on top of each other.

The new stuff is better thought out but their refusal to version CSS means the early mistakes will be with us forever. We can't move on.

In JS at least they used "use strict" to move the language forwards. That was clever. I wish css would do the same.

@teleclimber I don't think you can compare CSS to JS directly. You need to compare CSS and JS + all of its browser APIs (which are largely a shit-show).

Also note that I said 'least bad'. That doesn't mean that it isn't a bit of a mess. It means that the other two parts of the browser-based stack (HTML and DOM) are worse and _more_ confusing.

So I think we'll have to agree to disagree on this.

Sign in to participate in the conversation

One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!