Another loser here to second you

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

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?"

And that’s not true! He did want to keep the editor stable and available for many platforms and compatible with vi. Rejected proposals break one of these rules.

do you mean http://cream.sourceforge.net/

Merci.

I loved using it to write and browse my html files. It can do troff too <3

No, the editor is "ex" (for extended ed…) and "vi" is it's other face… (when you call vi, it’s same as calling ex then issuing :visual command…)

And they're "codenames" not supposed to be as obvious as names…

That's because "ed" was the "editor" (and that later was abbreviated "ed"…) when sed born.

As unique as: Go, Python, R, Rust, Word, Writer, --"

And before the rise of heavy IDE, you need some coffee to write all those SomeObscureWord.longLongStuf.notSoShortOne.LastSentence()