The Road to Emacs Maximalism(schonfinkel.github.io)
schonfinkel.github.io
The Road to Emacs Maximalism
https://schonfinkel.github.io/blog/20241230-the_road_to_emacs_maximalism.html
5 comments
> how might Emacs evolve to seamlessly integrate these technologies
Packages will fill the gap. There are no shortage of AI experiments/packages out there. I author one. https://lmno.lol/alvaro/chatgpt-shell-goes-multi-model
Packages will fill the gap. There are no shortage of AI experiments/packages out there. I author one. https://lmno.lol/alvaro/chatgpt-shell-goes-multi-model
The AI stuff these days is probably the easiest type of thing for Emacs to replicate, since all of the APIs are essentially just passing in and parsing strings of text. May more easy than IDE-like features and easier than LSP.
Like, no one would need to form Emacs to support all of the features Cursor provides. VSCode had to be forked and lost a considerable user-base to it.
Like, no one would need to form Emacs to support all of the features Cursor provides. VSCode had to be forked and lost a considerable user-base to it.
Emacs maximalism is the way to go. I spend most of my free time at my job re-implementing all of the companies internal tooling in Elisp, along with integrations using the Jira/Gitlab API, and also random automations that I need/want.
Then there is org-mode containing a record of everything I worked on with all my notes, executable scripts, all my time tracking information, org-roam notes, auto-generated request libraries using the verb package, literate API request documents for each micro service, etc.
It's such a good feeling when every tool can interact with any other tool in a variety of ways and that in a few keypresses you can modify and fix anything.
Then there is org-mode containing a record of everything I worked on with all my notes, executable scripts, all my time tracking information, org-roam notes, auto-generated request libraries using the verb package, literate API request documents for each micro service, etc.
It's such a good feeling when every tool can interact with any other tool in a variety of ways and that in a few keypresses you can modify and fix anything.
Glad to know I'm in the right direction then! ;)
However, with the rapid rise of large language models and AI-driven development tools, how might Emacs evolve to seamlessly integrate these technologies—such as AI-assisted refactoring, code completion, and knowledge management—while still preserving its core values of extensibility, user freedom, and community-driven innovation?
Other tools seem to have better AI integration. I might be wrong.