@c0debabe sorry ... this stuff gets me angry.

@catraxx the early web was cooler. people could learn from each other. oh how did they do that? *look at the code*

@c0debabe I mean as if i can't still steal everything i want. This is is so pointless, it only makes it a pain to look at. They must feel so damn clever ...

@catraxx "html-div"

?????

`div {}` as a selector is right there??

@ShadowJonathan complete disaster ...

@catraxx what site was this on btw

@ShadowJonathan Instagram

@meluzzy @catraxx they're using stylex, a css-in-js library, there weren't any class names to obfuscate to begin with

@meluzzy @catraxx hot take: i don't see what's so criminal about this

@107d @meluzzy I mean starting with css in js which i do not like whatsoever, this is utterly unreadable. And it is a consequence of forcing js into an area is has no business being involved in.

@catraxx @meluzzy not liking css in js doesn't necessarily mean nobody should ever use it though, and the resulting html isn't for users to look at anyways so i don't see why it necessarily has to be readable

@107d @meluzzy because why wouldn't it be? For the perceived advantage of putting css with the js? This can so easily be made readable, in which case you would quite simply make the code more understandable for everyone.

@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.

@catraxx @c0debabe i doubt the intended use case was to prevent reverse engineering. maybe a happy side effect, but that just looks like tailwind (or similar) & a name mangler (generally for avoiding clashes but well, not required if you're using tailwind)