3 ms·

emacs just need to things * make it fast (magit is the benchmark, if magit becomes fast emacs is fast, for those who dont know magit is slow, very very slow)

emacs just need to things * make it fast (magit is the benchmark, if magit becomes fast emacs is fast, for those who dont know magit is slow, very very slow) * add more UI stuff (graphical tree browsers, tables , etc ..) the core concepts and main UI of emacs are the best there is in my opinion, simple, uncluttered , logical

dingnuts 3y ago
curious if you're using nativecomp or not? magit does not seem slow to me and while I do use it on real repositories I do not use it on any insane monorepos or anything like that
smackeyacky 3y ago
It could also use a decent editor
SoftTalker 3y ago
I find emacs moves plenty fast for my human brain. Including magit, anything to do with git slows my brain to a crawl anyway. I get that it might be slow if you're trying to use it to automate something complex, as some part of a server, etc. but it more than keeps up with me.
nequo 3y ago
With regards to Magit being slow, are you using it on Windows?
- systems 3y ago
  yes
  - nequo 3y ago
    Then the slowness that you're seeing is probably Windows-specific, and that's why everyone else is telling you that Magit is actually fast. WSL might make things faster.[1] IIUC, the problem is that starting new processes is much slower on Windows than on Linux/Unix and Magit relies heavily on that. This seems to have plagued Git tooling more generally but maybe this got fixed since then.[2] [1] https://emacs.stackexchange.com/a/58444 https://emacs.stackexchange.com/a/58444 [2] https://github.com/magit/magit/issues/2395#issuecomment-171023551 https://github.com/magit/magit/issues/2395#issuecomment-1710...
logicprog 3y ago
Magit is plenty fast for me personally. Near instant even. As for UI stuff, I'm not sure what you mean — it does have a file tree sidebar minor mode, and it can display images and tables and so on in Markdown or Org
- systems 3y ago
  yes things like the tree sidebar, i think those UI element can be improved, again magit can be used for benchmark, this can improve the log viewer make it look nicer
iLemming 3y ago
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.

dingnuts 3y ago

curious if you're using nativecomp or not? magit does not seem slow to me and while I do use it on real repositories I do not use it on any insane monorepos or anything like that

smackeyacky 3y ago

It could also use a decent editor

SoftTalker 3y ago

I find emacs moves plenty fast for my human brain. Including magit, anything to do with git slows my brain to a crawl anyway. I get that it might be slow if you're trying to use it to automate something complex, as some part of a server, etc. but it more than keeps up with me.

nequo 3y ago

With regards to Magit being slow, are you using it on Windows?

systems 3y ago
yes
- nequo 3y ago
  Then the slowness that you're seeing is probably Windows-specific, and that's why everyone else is telling you that Magit is actually fast. WSL might make things faster.[1] IIUC, the problem is that starting new processes is much slower on Windows than on Linux/Unix and Magit relies heavily on that. This seems to have plagued Git tooling more generally but maybe this got fixed since then.[2] [1] https://emacs.stackexchange.com/a/58444 https://emacs.stackexchange.com/a/58444 [2] https://github.com/magit/magit/issues/2395#issuecomment-171023551 https://github.com/magit/magit/issues/2395#issuecomment-1710...

logicprog 3y ago

Magit is plenty fast for me personally. Near instant even. As for UI stuff, I'm not sure what you mean — it does have a file tree sidebar minor mode, and it can display images and tables and so on in Markdown or Org

systems 3y ago
yes things like the tree sidebar, i think those UI element can be improved, again magit can be used for benchmark, this can improve the log viewer make it look nicer

iLemming 3y ago

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.