Seriously ....
-
@catraxx @107d There is an advantage to CSS in JS, It makes it easier for a big development team to handle styles.
Frontend web development can get very chaotic very fast if not handled correctly.
In my previous job we had LESS mixed with SASS mixed with react-css-classes mixed with native .css imports mixed with Tailwind mixed with Bootstrap... It was a nightmare because everyone just came and did waterver they felt like it. So actually imposing something that forces all CSS to be done in a very specific way saves a lot of disasters from happening.@meluzzy @107d I disagree. Using less and sass together in a project already requires two separate preprocessors and i can just as easily do that is js if i want to. Simply putting it in the js will not save you got to make sure everyone understands the rules.
I also saw the opposite: backend devs fuzzing about in the styling, which they neither had the permission two, nor the knowledge for, but "because it was right there", they would simply mess around in it.
As a frontend dev, i vastly prefer the css to be entirely separate, in small files that match the component i am working on. Putting it in js complicates everything, makes it far easier to break and less readable in bigger files.
-
@c0debabe Yeah because oooOOOOooo scary, we encode the classnames so you can't reverse engineer or shitty slow as fuck, piece of absolute shit website.
