Love this! Looks nice (I can't design it), works smoothly. Kudos on you for building something simple and just getting it out there.
Universe knows, there are many bells and whistles you could have tacked on, possibly dooming this project to stay in the "project shelf" for a much longer time.
What's your story on starting this? Needed the tool yourself and couldn't find anything that worked for you, was trying to learn new tools, lost a bet?
Felt (still am, actually) this problem too. Started with the same approach (Vanilla Emacs) a few years back in order to really learn the ins-and-outs after giving DOOM and others a shot and feeling like I didn't have the faintest what was really going on with all the magic. I somehow did end up falling in love with Emacs again[^1].
Won't lie... there was a fair amount of cursing involved and, despite the love, I wouldn't recommend many to venture down this road[^2].
> Unsolicited tip: Take it as a hobby! Picked up a bunch of useful learnings from my Emacs experiences (a. literate configs, b. comfort around working with LISPs, c. bigger appreciation for parts of the GNU ecosystem, d. more in-depth understanding of how my devtools work which helps me debug issues in Neovim or vscode when I see them) but still think that I'm cursed by wanting to go down this road so badly. Wish I could just vscode my way through life and build dope stuff, unencumbered!
P.S.: I found Emacs far less painful ever since I started rubber-ducking with ChatGPT about my elisp and configuration problems a few years ago, so now is definitely a nicer time to take the plunge.
1: Used Emacs heavily in college over 12 years ago when I would boot the Windows + Novell groupware school computers into my own Ubuntu config with my Emacs and embedded dev toolchain from my pendrive.
2: The single-threaded-ness and related ocassional unresponsiveness/hangups still grind my gears.
From a pure business perspective, I feel like there are more data points out there that have won (as in, "survived") by shipping proprietary software.
Don't want to make moral judgements here about proprietary-vs-FLOSS but within my hacker bubbles, one biases themselves to be partial to FLOSS very easily. If I were to ship "some things" (it really depends what the thing is) as proprietary, this community may not take too kindly to that move (and neither may I).
On the other hand, I don't think that the world at large really cares. Sometimes it feels that one can either be a) financially well off or b) more beloved by the hacker community. These things are not mutually exclusive like that but the union of these is rather rare. Hard choices!
Universe knows, there are many bells and whistles you could have tacked on, possibly dooming this project to stay in the "project shelf" for a much longer time.
What's your story on starting this? Needed the tool yourself and couldn't find anything that worked for you, was trying to learn new tools, lost a bet?