Follow

Moving CSS into JS adds a barrier preventing people not already deep in JS land from styling stuff. Doing CSS the classical way means you lose the advantages of JS infrastructure (dependency management, avoiding a global namespace). For authors of generic components, both suck.

I'm hitting a bit of a wall here github.com/codemirror/codemirr

@marijn
I know what you mean - CSS isn't enough. The JS looks very ugly, because anything that changes the DOM looks really horrible without JQuery. It's a pain

@marijn @baldur I thought that moving CSS into JS was a thing from around 1998 ... and JSSS died with the Netscape Communicator.

@marijn CSS in JS should always be the last option. You got to do something like that for distributed components, but I don't see why people do this to themselves when they build a single website.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!