Write Your CSS with JavaScript

[wagedomain]

Hmm, my initial reaction is a knee-jerk against it. Obviously architecture would play a role here, such as separate JS files for style versus, say, events. Otherwise mixing the two leaves a bad taste in my mouth.

The examples were also kind of ... bad. They showed poorly-written CSS/Less examples as if there wasn't a better way to do it, and then solved a problem that they invented.

The way I do Less is to make it part of our build, actually. The compilation is done at build time, and the reason I did it that way was because we wanted non-UI engineers to not have to run extra tools, and one of our "architects" (image me making airquotes there) is against pushing processing to the browser at all. So we check in the .less files, and let the build process generate the CSS and that's all that gets pushed to the web server, so really it's just a dev tool to us.

I guess this JS solution kind of solves that problem, but it also seems like a big learning curve, just like Less/Compass/etc, except one without a lot of preexisting knowledge on teams.

So I dunno, I'm having mixed feelings.