2 ms·
It's a choice. The dominant paradigms choose not to. I disagree. And that makes me the loser here
by kristopolous 8mo ago
It's a choice. The dominant paradigms choose not to.
I disagree. And that makes me the loser here
- gilcot 8mo agoAnother loser here to second you
- kristopolous 8mo agoI wrote these libraries like https://github.com/kristopolous/db.js https://github.com/kristopolous/db.js and https://github.com/kristopolous/evda 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
- noduerme 8mo agoAh, 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?"
- namuol 8mo agoI 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.