I've often wondered when Emacs would become the term used to describe hyper-personalized software. While it is true that LLMs give access to software that fits like a glove, it seems to me that there is still a glaring difference -- at least when one looks at GNU Emacs: a shared software tradition. To my knowledge [1], LLMs don't provide that.
Maybe it's best to call this movement in LLM-generated software "software individualism" rather than "personal software"?
[1] I don't know much as I haven't vibecoded before, and my .emacs is painfully crafted by hand.
Regarding the Novus Ordo, I believe that the key document from Vatican II (Sacrosanctum Concilium) still preferred Latin as the dominant language in liturgy, while readings etc. stayed in the vernacular, but clearly that is not what happened.
There's been an uptick in numbers for Tridentine Rite, so tides might shift back as Catholics realize the wealth of their liturgical tradition.
Emacs is a seemingly [0] excellent compromise between modern TUIs and accessibility since it keeps the text-centric paradigm but allows for much cleaner accessibility. [1]
[0]: I do not need any accessibility features myself.
If anyone is interested in playing around with this wonderful tool, there's an online editor (edit: no affiliation). [1] It is much more responsive than compiling in TeX.
Djot is great so far, and I'm eager to switch to it from Pandoc Markdown since editor support for Pandoc Markdown is lacking.
Looking at the repo's issues, I'm a bit concerned that it's already fragmented since some enthusiasts have implemented features far beyond, or against, Djot's spec. People seem impatient for v1.0...
I wonder if I'll ever see the day when Emacs's several terminal implementations are unified. How nice would it be if one could use term.el with libvterm, libghostty etc. as a backend?
On another note, as a light terminal user, I've had great success with MisTTY. [1]
> That is usually configurable at the terminal level
And if you use Emacs, it's configurable at the buffer level. [1] This lets me build a version of Iosevka where `~=` and `!=` both become ligaturized but in different major modes, avoiding any confusion.