TMA, multiply neurodivergent, ancient by internet standards, poylam and happily married.
I was on Cohost from 11/04/2022 until its last day (10/01/2024)
minified javascript in particular infuriates me, but obfuscated web code too. I understand that you gotta make money, but 90% of these things are selling services, not websites.
the current web boom is on the backs of the generation that could right click view source on amazon dot com in 1999, and we've let down every subsequent one by letting people pull that ladder up in the name of business interests (or performance, where we minify instead of pushing less bloat, due to business interests).
as a developer, i much prefer writing tailwind-style text-blue-500 p-4 classes because they are so much less likely to break child nodes. back when i used to write css manually, i would often end up with styles that are very dependent on the shape of the dom tree. and then i want to change some background effect or something. it's easy to do if you insert a wrapper div, but if i insert a wrapper div, everything breaks. tailwind classes are so much more predictable for me. like, there's probably some level of css-making discipline you could get to so that wouldn't happen as much, but i clearly don't have it.
as a user writing custom stylesheets, tailwind stuff isn't as nice but it's so much nicer than those elements__Wrapper-sc-4gy1pz-0 gQnPtz elements.
if inserting a wrapper div breaks everything then yes, something has gone horribly wrong somewhere. that's generally not how css works.
it's stuff like designing layouts with a grid. there is the parent div that defines the grid and then all the children that are positioned relative to the grid, and now you can't wrap those children because they need to be in the grid and it will mess up which slot they are in. so you have to move the grid into the new child node or something like that
or eg if you want to style a text block a certain way, so you target a selector like .prose p but then you embed a component inside of one of the paragraphs or elsewhere in the prose tag and all the styles are wrong because they got overridden by that prose class. now you have to either get rid of that entirely or override a whole bunch of things on random classes that you shouldn't have to deal with. or do the mess tailwind css is doing with some selector that allows you to embed no-prose inside prose and cancel all the effects
