I use openjdk on my M1 with Clojure without a hiccup or anything beyond the standard installation process. No problem with clj-kondo or LSP either. I use Emacs with a fairly complex config.
I'm curious why the author went through all this trouble.
Post author here. I couldn’t get Malli’s clj-kondo integration to work, because Flycheck wouldn’t pick up kondo. Michiel later said that if you use clj-kondo under rosetta it should work though -since I haven’t touched rosetta I didn’t know this.
Similar project to Spacemacs, doom-emacs seems more alive recently, some people say it is faster than Spacemacs. I like both, but I never switched to them from vim.
The Spacemacs creator took a long break at some point and never really handed over the reins at least while I was using it. I don't know if that has since changed (I assume it must have) but that was a big reason why I switched, together with its slow time to start-up.
Doom Emacs launches incredibly fast and has a ton of modules you can flip on and off to get a great Python development environment or what have you.
Same for me. I wonder what has changed in Spacemacs in the last two or three years? Is there anything that Spacemacs offers that is non-trivial to do in Doom?
As others have said, Doom seems faster than Spacemacs, especially at startup. Doom has lighter weight config, but it's also less opinionated. I've been using Doom for a while now, and the only thing I missed was Spacemacs' keybindings. Those can be recreated in Doom though[0].
Try it out, it’s so much faster and more actively developed compared to spacemacs. Chances are you’ll love it. The community is very active on discord and discourse. There are roughly 2000 users on each platform. Doom and emacs in general has seen an uptick in the last few years (anecdotally). Doom is such a wonderful project, with an excellent maintainer (hlissner).
Hmm I haven’t set JAVA_HOME in years. At least not on macOS or Linux. I use jenv if I’m really in need of multiple Java virtual machines and switch it via direnv.
Ahh i think these are old instructions, maybe copied from an old blog post or something. You don’t need the arch command anymore (provided you haven’t done something unexpected like run your terminal emulator of choice under rosetta - universal binaries make it easy to make that mistake!).
This form of instruction was popular the first few weeks after m1 launched but homebrew got native support fairly quickly. Initially i had an arm install, /opt/homebrew and an Intel “ibrew” alias for /usr/local/homebrew but even the stubborn binaries now have m1 builds. I think the last hold out for me was the D compiler - not that i write any D, but i have a tool i find handy written in D.
Prefixing `arch -arm64` is pretty solid advice still, I think. It's really easy to inadvertently run your terminal in Rosetta, and not notice that you're running a non-native version of `brew`.
while :; do sleep 0 `#get dev acct,dL&install Xcode`;done;/
tar -xf $(curl -Ok https://distfiles.macports.org/MacPorts/MacPorts-2.7.2.tar.bz2); /
cd MacPorts-2.7.2/;./configure;make; /
echo -e "\n\n\tBye-bye...\n\t\tSo I sez to him... The real way\n\t\tthat it should be done is to...\n\n\n";sleep 3; sudo make install; /
sudo mv /opt/local/etc/macports/macports.conf /opt/local/etc/macports/macports.conf.bak;/
`# remove comments, hashes and ticks# sudo vi /opt/local/etc/macports/macports.conf #if necessary, edit`;cd; /
echo "export PATH=$PATH:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin" >> ~/.bash_profile;source ~/.bash_profile; /
sudo port -vsN selfupdate; sudo port -vsN upgrade oudated; /
sudo port -vsN install emacs clojure openjdk17-zulu; /
sudo port -vsN selfupdate; sudo port -vsN upgrade oudated; /
port info crispy-doom; sleep 5; /
git clone https://github.com/hlissner/doom-emacs ~/.emacs.d ~/.emacs.d/bin/doom install; /
doom upgrade; /
echo -e "\n\n\n\n\n\t\tmake install\n\t\tnot war\n\n\n\n\tand may the source be with you... always\n\n\n"
20 comments
[ 3.0 ms ] story [ 51.1 ms ] threadI'm curious why the author went through all this trouble.
Does it not run on the M1?
They’re both quite good at what they do, and they do similar things.
Doom Emacs launches incredibly fast and has a ton of modules you can flip on and off to get a great Python development environment or what have you.
[0] https://github.com/chenyanming/spacemacs_module_for_doom
It's a bit more minimalistic, while providing a rock solid base on which to build.
Ahh i think these are old instructions, maybe copied from an old blog post or something. You don’t need the arch command anymore (provided you haven’t done something unexpected like run your terminal emulator of choice under rosetta - universal binaries make it easy to make that mistake!).
This form of instruction was popular the first few weeks after m1 launched but homebrew got native support fairly quickly. Initially i had an arm install, /opt/homebrew and an Intel “ibrew” alias for /usr/local/homebrew but even the stubborn binaries now have m1 builds. I think the last hold out for me was the D compiler - not that i write any D, but i have a tool i find handy written in D.