I am excited by this. I tried it a few months ago, then switched to a M1 Mac and went back to a current stable version. I find IDEs that are M1 native are noticeably faster. I look forward to a M1 native libgccjit Emacs.
Bringing GNU Emacs to Native Code (2020)
11–20 of 138 posts
Re: Bringing GNU Emacs to Native Code (2020)
#12Getting much better fps in Doom in Emacs now.
Re: Bringing GNU Emacs to Native Code (2020)
#13I have really liked native-comp so far on Arch Linux. I think in the last year or so I have had total two hiccups only due to nativ-comp.
Re: Bringing GNU Emacs to Native Code (2020)
#14Getting much better fps in Doom in Emacs now.
This is my favorite comment of the day! Kudos :) I don’t care if it gets downvoted by guidelines lawyers
Re: Bringing GNU Emacs to Native Code (2020)
#15Getting much better fps in Doom in Emacs now.
Is there a Doom module for this?
Re: Bringing GNU Emacs to Native Code (2020)
#16Re: Bringing GNU Emacs to Native Code (2020)
#17Getting much better fps in Doom in Emacs now.
Is there a Doom module for this?
He's talking about Doom Emacs: https://github.com/hlissner/doom-emacs
Re: Bringing GNU Emacs to Native Code (2020)
#18Every time I try Emacs I get annoyed by it's slowness and go back to vim and VS Code.
This might entice me to build it and try out my Emacs Doom setup again.
Re: Bringing GNU Emacs to Native Code (2020)
#19Every time I try Emacs I get annoyed by it's slowness and go back to vim and VS Code. This might entice me to build it and try out my Emacs Doom setup again.
hell yeah me too, this will make it get back to Emacs again :D
Re: Bringing GNU Emacs to Native Code (2020)
#20It makes LSPs usable for me on my desktop 5950x. Still a bit laggy on my laptop.