CSSWind: bloat-free component styling
1 points by sloane
1 points by sloane
The end result here may mean the toolchain for building your site is less bloated, but it for sure makes the resulting HTML look way more bloated. Not that anyone is actually reading plain HTML I guess...
Maybe I'm crazy, insane, bonkers, but I always prefer writing my own CSS from scratch basically (I enjoy it!). I hate inline styles and I hate component styling like Tailwind, et al.
writing css completely standalone always frustrates me, probably because i don’t understand it as well as i should. my brain always wants the styles more localized to the corresponding code, albeit not intertwined or coupled to the logic itself
the best experience i can think of having with css was around when i graduated college, doing some stuff with Vue.js components which had isolated, per-component stylesheets. i never stuck with doing webdev, and the code i wrote was probably bad for other reasons, but i do recall enjoying the experience of doing styling “more locally”
css constantly vexes me. tailwind vexes me even more. i first read this post as sort of tongue in cheek, but the author has actually used the technique, and it is visually quite similar to the result of using tailwind… i’m curious about what the tradeoffs and implications of using this approach would be