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.
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!
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
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!
I imagine Emacs gaining native compilation capability took some pressure off that. But the appeal of scripting Emacs in languages other than Elisp still has some appeal, I think. Scheme or Lua would very nice for that purpose.
EDIT: There it is - https://emacsconf.org/2024/talks/guile/
There have been a couple of front-page threads on Lua recently and their comments really show how polarizing of a language that one is
I am a guile person, but even if the Emacs folks would only allow elisp on guile it would still be a win.
It'd be good to see this (or something better!) make progress.
[1]: https://github.com/emacs-eaf/emacs-application-framework
This is the main reason I use it as well.
Emacs is far from perfect. It's slow, lacks some of the bells and whistles of other editors, and can be downright frustrating to use at times.
But damnit, it's _mine_. It has allowed me to create the perfect editing and programming experience _for me_, and no other environment gives me that freedom and enjoyment. Vim and friends come close, and I continue to use it as my secondary editor (and couldn't function without vim-mode), but Emacs allows much deeper customization and Lisp is so elegant for this.
As editors come and go, it's comforting to know that Emacs will always be there for me. Warts and all. <3
For those not familiar, Lem is very approximately an Emacs, natively written and extendable in Common Lisp, multiplatform, NCurses & SDL2, etc. LSP. And fast.
I'm a happy Emacs user, but think having more options is great, and I've delved into some Common Lisp and certainly am eager to learn more. So I'm thrilled to see Lem continue to be developed.
https://emacsconf.org/2024/talks/casual/ -- Charles Choi designing UIs for human beings rather than octopuses (this jibe is meant fondly, I am a happy octopus)
https://emacsconf.org/2024/talks/literate/ -- Howard Abram, literate programming
https://emacsconf.org/2024/talks/gypsum/ -- Emacs and emacs lisp clone in Guile
https://emacsconf.org/2024/talks/rust/ -- Rune, an experimental Emacs core in Rust
https://emacsconf.org/2024/talks/julia/ -- lovely talk about the synchronicity between Julia and Emacs
https://emacsconf.org/2024/talks/guile/ -- Robin Templeton relaunches Guile-Emacs!
https://emacsconf.org/2024/talks/mcclim/ -- eh, this talk accepted questions from lambdaMOO?
How does this compared to all other conf costs?
Very cool though, that they managed to pull it off.
We've been experimenting with sending tokens of appreciation (evil plan: stickers/pins might get other people to talk to speakers about Emacs), but Corwin's treating that as a personal experiment and not including it in the conference budgeting.
And of course, there's a lot of stuff that isn't counted in monetary costs, like the time that speakers put into their talks or the servers that people have shared with us.
But yeah, it's surprising what you can do on a shoestring budget and with casual volunteers. Definitely worth considering if people have been thinking about running their own conference. :)
I did it the other way, and going back to elisp is /hard/.
Although this, from the page linked, was pretty fun: https://www.youtube.com/watch?v=urcL86UpqZc
Feels sad. And also potentially shortsighted.
I think Emacs users care more about the total population than one particular outmigration.
I don't have actual data, but if I compare to the amount of activity (blog posts, tweets/toots, packages, etc), then (heavy) Emacs usage seems to be monotonically increasing.
Almost everyone I know who switched to VSCode was using Emacs primarily for work, and mostly limited to SW development. That category of users may be large in absolute numbers, but most of the Emacs ecosystem is not driven by that category (i.e. even if that category shrinks to a tenth of its size, it won't have any impact on Emacs development).
Just take a look at the talks in the conference. The vast majority are orthogonal to SW development/programming.
I don’t even think VSC is “that” bad despite what I made it sound like, but it’s probably as temporary as any other modern IDE. In a few years “every” VSC user will probably have moved on to Zed. Meanwhile your emacs (or vim) dot files will setup the only IDE you’ve ever used on any machine.
I don't think there's an argument to be made that we're at risk of losing something. So much of editor progress in the past ~years is shared -- treesitter, lsp backends, linters and snippets, etc. It's hard for me to imagine how the editor ecosystem could collapse.
> And also potentially shortsighted.
Looking at the recent releases, it feels like the vscode enshittification has already begun...