My guess is, that writing Emacs packages requires a lot of discipline, to only use the minimal surface one needs from Emacs. And that is, because of the huge amount of mutable global state in Emacs. An actual design flaw, that is sometimes super useful, but at other times super annoying.
replyQuestion: Why VSCode spyware? Why not at least VSCodium? Or is this just a case like people saying Chrome, when they have Chromium or Ungoogled-Chromium?
replyLLMs are a godsend in fixing emacs problems.
replyBoth you and the sibling common by buzzwords have the same contexte: You’re both using someone’s configuration framework, which goes bery much against the vanilla emacs’s way. Most package assumes something standard and you can expect something to break if your configuration isn’t.
replyI've used Doom Emacs for years and it rarely breaks. Sometimes things get out of sync, and I delete the git repo and clone it again. That happens once every few years.
replyPeople holding your attitude is one thing that keeps people away from Emacs. Very few people want to get into the weeds of customizing their editor. They want to do whatever it is they are interested in and the editor is tool to get it done. Doom Emacs, and other approachable "distributions" are the way to make the power of Emacs accessible.
> You’re both using someone’s configuration framework, which goes bery much against the vanilla emacs’s way
replyI heard a similar argument about vim's billion configuration options.
At some point I simply got tired of having to tweak it and switched to a better editor (not emacs though; both vim and emacs are losing in any debate, but it's a fun debate nonetheless since both camps think software can only be written with these two editors; everyone else must be clueless and skillless).
Spacemacs is kind of bloated and easy to break with custom packages which are not part of original build
reply