NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


feeling like even though I know nothing about the underlying language i should probably learn how to write vscode addons

I would learn elisp instead, because I really would prefer emacs' modifiability but emacs has too much keyboard dedicated to functionality I'll never use with their specific bindings, while making it arduous to start from basic ones and build them up, when i'd rather my tools fit my hands

(yes, modes can be defined on a case by case basis, but vscode has much easier per addon and per-category and per-pane separations from what I've looked through)


You must log in to comment.

in reply to @NireBryce's post:

my problem isn't with elisp as much as emacs. i like elisp. i like what emacs was mythologized to be. I'm so sad that the current ecosystem and cult of keybinds has ossified a lot of it in ways that are hard to extract and manipulate without cascading failures, mostly around keybindings, and the need for my editor to work fast enough for me to be able to learn it through use and incrimentally bind things, not be a hobby car, or a hobby car I remove the internals of and painstakingly replace with my own