News for hackers. Stuff that matters.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by kristopolous on Sunday February 15, 2026 @08:23PM (#47029774)
It's a choice. The dominant paradigms choose not to.

I disagree. And that makes me the loser here

Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by namuol on Sunday February 15, 2026 @11:23PM (#47030866)
I agree, it’s a choice. So is the opposite. Complaining about other people’s choice of doing things on the web is the choice I’m actually tired of.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by samastur on Monday February 16, 2026 @07:53AM (#47034388)
Read something else then.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by namuol on Tuesday February 17, 2026 @11:47PM (#47057277)
I’m a web developer by trade. I read about it. Sorry?
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by samastur on Thursday February 26, 2026 @04:04AM (#47163686)
I am as well and there's no shortage of relevant content to fill my whole day so I can skip articles I dislike.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by gilcot on Sunday February 15, 2026 @08:53PM (#47029993)
Another loser here to second you
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by kristopolous on Sunday February 15, 2026 @09:05PM (#47030080)
I wrote these libraries like

https://github.com/kristopolous/db.js and https://github.com/kristopolous/evda in the early 2010s. I spent months on them

I was all in. I swore off touching front end in 2022. It's terrible now

Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by noduerme on Sunday February 15, 2026 @09:51PM (#47030343)
Ah, yeah. I spent the early 2010s writing front-ends in AS3, so imagine how that turned out. I wrote my own event system too when I was forced to head to javascript, but in the end I mostly just used jquery's, and it's still what I use. I agree the event-driven paradigm leads to sloppy code, but static event names are enough of a clue to what's invoked most of the time, even in relatively large projects. And most things can sensibly just be promisified now anyway, besides user interactions.

I thought it was funny that you wrote this way back when:

>> I've often seen projects where I think "what talks to what and how? What is the separation of concerns and where does this code live?"