Post by @slightlyoff@toot.cafe

RE: https://social.vivaldi.net/@brucelawson/117387522243320669

While I can't claim any credit for the GH move -- their choices appear to be a random walk through a museum of footguns -- I did give an internal talk earlier in the year titled "CSS-in-JS: Frontend's Worst Idea?". You can probably predict the contents: massive memory and processing overhead, style invalidation a-go-go, etc.

What's worst about this entire debacle is the gutting of engineering culture. Bros picking stacks on GH stars and twitter whuffie. Every repair is harder now.

0 Boosts

0 Likes

Bryan

@btopro@mastodon.social 10 hr. ago

@slightlyoff I hope we're not considering webcomponents w/ constructable stylesheets as css in js cause... I'm not getting off that drug :P

ᴀʟᴇx ʀᴜssᴇʟʟ

@slightlyoff@toot.cafe 4 hr. ago

@btopro we're not, for boring reasons I can get into, but suffice to say the folks making these messes won't understand what you typed or my response, so we're safe.

Jencel Panic

@abuseofnotation@mathstodon.xyz 11 hr. ago

@slightlyoff I started reading about it, but I don't really understand the problem these guys are having.

When I worked front-end, we just... wrote CSS.

If you want to have a component with a specific style you just... made up a name for the CSS class of that component...

I don't remember experiencing a name-clash but if I ever did, I probably just change the damn name...

What happened to software?

charlag

@charlag@birb.site 11 hr. ago

@abuseofnotation @slightlyoff if I may

you want to write a library (internal or not) of UI components. you want to only ship the styles that are used and ideally only load them at the time the relevant component is used. how do you do this?

ᴀʟᴇx ʀᴜssᴇʟʟ

@slightlyoff@toot.cafe 11 hr. ago

@charlag @abuseofnotation first, reset your understanding of what the differential costs between too much JS and too much CSS are. These are not the same, and this confusion sits below many mistakes.

ᴀʟᴇx ʀᴜssᴇʟʟ

@slightlyoff@toot.cafe 14 hr. ago

And I don't mean "harder" in the sense of putting the semicolons and braces in different locations; refactoring has never been more automated.

Thing have gotten harder to fix because entire layers of management are now fundamentally unfamiliar (best case: rusty) with the evidence-based decision-making necessary to nurture a healthy product culture. Some never got promoted for doing an objectively good job; starting from zero. It's pushing molasses up a hill with this sort.

Zeh Fernando

@zeh@mastodon.gamedev.place 12 hr. ago

@slightlyoff Nice.

At this point I'm surprised, but glad, it's not tailwind, which is just a different form of cancer.