Magit is not slow. At least the components that make Magit are not slow. transient, magit-section, forge, etc. are not slow. Magit delegates things to Git, and

Magit is not slow. At least the components that make Magit are not slow. transient, magit-section, forge, etc. are not slow. Magit delegates things to Git, and that can be slow in certain cases on specific environments. Learn how to use built-in Emacs Profiler to find things that make it sluggish. For example, Magit tries to display tags (in addition to branches) in the refs buffer, for the project that has too many, yeah, that may be slow. The solutions is simply to remove the hook (remove-hook 'magit-refs-sections-hook #'magit-insert-tags) It's just a single, isolated example. People complaining "Emacs is slow", is like choosing to drive a nail with the handle of a screwdriver and complaining how hard that is. Well, maybe learn how to use the tool, no? Emacs is a Lisp machine made to run Elisp byte-code. It's not a final product built with some C and Elisp that you may never need to learn. You do need to have at least some basic understanding of Elisp. Even if someone is impatient, they could develop inner curiosity and type in ChatGPT "what happens when Emacs opens a buffer". Basic understanding of standard hooks and hooks in general, advising functions, etc. is all required for you to be the "user of Emacs". No wonder we see people claiming to have used Emacs for over a decade and still switching to VSCode. Turns out, most of them never wrote a single Elisp package, or ever understood how some copy-pasted magical elisp snippet ever worked. I can't claim to be a chef or even good at cooking if all I ever do is microwave pizza. Even if I did that for twenty years. I'm not saying that everyone using Emacs should know how to setup Gnus, master keyboard macros or should be able to whip up a new minor mode in zero-gravity. But please try the built-in Profiler. Learn how to use describe-command, describe-key, etc. It is not that difficult.