well this fucken sucks. I was rooting for the dude and his projects.
i'll put myself out there - here's a receipt from 06~07 https://web.archive.org/web/20070512035940cs_/http://www.toyota.com.au/toyota/main/css/elements.css
we were a team of 5 devs including me. We weren't tribed off into separate areas of concern, we all knew the whole project back to front, and (maybe not the most clever move) managed without version control by always being aware which part we were working on. Cos, ya know, communication is easy when you are 5 people sitting in a group.
Don't give me shit about the complexity of the UI in modern apps either. We were dealing with a huge collection of brochure style pages that had plenty of variations. We kept all that css under 500kb. We could achieve the bland flatness of modern uis under 100kb easily. No fucking doubt.
Modularity also allows for code reuse. It increases maintainability.
another thing to think about is how this was not invented by frontend frameworks. We did it fine pre-SPAs and pre-preprocessors. It was part of the architecture and strategy. The hard work that allowed us to essentially reskin entire, very complex, projects every couple of years
I know this sounds like old man shit, but I'll die on this hill. It's a significant fundamental attitude shift
I remember when we used to write our name in our css files because we wanted to, not because our ssh key enforced it for auditability
I love when someone argues against something that is arguing against everything they use in their argument
praise the circumstances that enable the scourge of b2b saas products imposed on employees at the collaboration factory
as a developer my favourite thing about react componentisation is how it makes me and my team more readily replaceable
I remember seeing an argument on reddit between a css dev that understood the depth of the responsive design philosophy and a dismissive Reacter that shut them down by calling them an old "list-aparter"
we used to strive for minimum possible front-end payload, and it was an embarrassment to do anything with JS that wasn't backed up by a non-js default. Will never forget how suddenly React removed all those things from front-end team meetings.
They were solid industry-wide concerns that just... disappeared
Mastodon, too, will not give you anything if you have JS disabled.
Is it absurd that the maker of a tech product controls it by writing it a list of plain language guidelines? or am I out of touch?