Thanks Sacha!
You know how it is... It's fun to write Emacs Lisp to automate things, smoothen my workflow, reduce the risk of mistakes. 15 minutes here, 5 minutes there... Micro-improvements add up!
ps aux | grep vi
People not knowing how to quit vim is a meme but at the same time is real as ever.There was an interesting discussion on Reddit after NeovimConf 2024 (https://www.reddit.com/r/neovim/s/TSFc3cVGGV) People were happy about the talks. Some seemed a little frustrated by interruptions from ads, getting off schedule, and a chat that might sometimes get a little distracted by meme potential. EmacsConf is a lot smaller than NeovimConf in terms of viewers - twitchtracker says NeovimConf got 3640 (plus more on YouTube) and we got about 400. We're, like, an order of magnitude smaller. That might be why self-hosting via Icecast is manageable for us. We started automating scheduling a few years ago because I wanted to accept more talks than could comfortably fit in a day, and since I was figuring out that infrastructure close to the conference, I needed something that I could handle by myself without going crazy. Even though my co-organizers are now more familiar with the fallback scripts for manual control, they prefer the automatic schedule. And community is a gift beyond anything I can code. I remember watching the IRC logs scroll past and feeling deeply appreciative of how wonderful and thoughtful people are, even during some of the tougher sessions we've had in the past.
Also we like doing captions and transcripts and putting up the videos as soon as possible. :) Text makes things easier to search and skim, especially from within Emacs. And videos, well, we've got them, we might as well have a little bit of code to publish them right away.
I reached out to teej_dv and ThePrimeagen on X to see if I could learn from their NeovimConf notes or in case any of our notes might be helpful. TJ said they don't really write things down. Makes sense because they're more video people. I hope they'll consider doing a postmortem braindump and maybe even sharing that publicly. I think that would be really cool.
For me, I lean heavily on automation, documentation, and incremental improvements partly because it's fun, partly because it helps me make the most of what little time I can squeeze in between interruptions, and partly because it ripples out and helps other people who often end up paying it forward. Emacs is very well-suited to this, of course. Every time we get to do EmacsConf, I learn even more and build up more tools along the way.
I think Vim and Neovim have a way bigger userbase than Emacs does, and I'm glad to see Neovim talks sharing workflows beyond the usual software development things. I do think there's something wonderful about the multiplicity of things that people use Emacs for, and how we've got this culture of both figuring out how to tailor Emacs to yourself and sharing those ideas with other people. I'd love to see what happens as Neovim and other editors build that critical mass of user configuration and community sharing, when people can figure out something for themselves by cobbling together stuff from other people. I think it's kinda cool how people shift from one editor to another, even. If they bring ideas from Emacs to somewhere else, or they bring ideas from somewhere else back to Emacs, things get better.
I'd love it if NeovimConf could also be a smoothly-running way to get stuff out of people's heads, connect people with other people, and inspire more awesomeness. I'd love it if people could do that sort of stuff with all sorts of other mini-conferences about their interests. Could be fun!
It gives me hope for the longevity of the editor, and indeed, in the short ten years I've been a casual user it has only gotten better.
Long live the Emacs community
EDIT: looks like even in this thread people are suggesting to use Lua instead of elisp. smh
Now imagine trying to explain to them the concept of subtracting a hundred from a billion and the most straightforward way to deal with that is a decimal numbering system. I think they'd kill you for blackmagicfuckery on the spot.
Well, if that comparison feels condescending, let's imagine ancient Romans - with all their sophisticated culture, economy and traditions. They wouldn't kill you, but still the idea of a number such a billion would probably terrify them. They'd probably be like: "dear sapientissime señore, we respect your wisdom, but we rather use... Lua"
Oh, I found the answer on my own, with the help of LLM. For a billion you can use M̅M̅, which technically would mean a thousand thousand thousands, and to denote the calculation above you'd write - M̅M̅CM. But my point still remains relevant - this is the modern extended version of Roman numerals. In ancient Rome they typically never would go up to a billion.
Probably Stallman would object that Lua doesn't have read (apart from eval) and print.
As for performance, LuaJIT performance is better than any Common Lisp or Elisp, and dramatically better than the first 35 years of Elisp, before native-code compilation.
XEmacs, much better than Emacs back then, was my rescue for not having IDE culture back in my early UNIX days. We're talking back when Xenix and DG/UX would be known names to anyone working with UNIXes.
Nowadays, while Emacs key bindings and elisp might still be burned into my brain cells, I no longer reach out to it.
Emacsconf was indeed executed great this year, and nice and cozy were my feelings too. It's interesting to compare and contrast the ambience between Emacsconf and that of the other editors' like neovim conf and the release "parties" of Visual Studio Code and Jetbrains.