5 ms·
Of course, anybody is able to manage a problem, but our jobs as engineers should be to fix the problem. And indeed, there is a lot that is problematic about CSS
by clessg 11y ago
Of course, anybody is able to manage a problem, but our jobs as engineers should be to fix the problem. And indeed, there is a lot that is problematic about CSS, just as there is a lot that is problematic about writing concurrent code in old versions of Java.
You can deal with it if you're careful and don't let anybody touch the code, but you've solved nothing and as an engineer, that should make you feel bad.
- tracker1 11y agoI'm not sure that this really solves the problem better than keeping your less files next to your jsx files for component specific styles and relying on css classes, hierarchy or properties as it stands. I've gone down the path of doing similar things to this, and in the end I find it's more complex than simply using less (or scss)... While I appreciate the effort actually inheriting styles in/out of react components, based on parent/child relationships is a lot harder to manage when dealing with your react components directly imho.
- clessg 11y agoAre you able to elaborate on what practical issues you ran into?
- tracker1 11y agoMainly centers around inheritance, or applying the same styles to multiple controls... it's much easier in CSS using classes, or hierarchies than it is directly in the controls... you'll usually wind up with some common js style files, and have to import/use them for reuse... and it just gets a bit weird, even compared to say bootstraps variables file.