Yup, this was it. I had introduced a syntax error that bugged cider but didn't bug shadow-cljs itself.

I'd say this guide applies https://clojure.org/guides/dev_startup_time ...I use my own, more automated variation of it . I'd say the official way is a bit manual However, when applied+understood carefully, it should be a good gain

It also can be a good idea to avoid as many requires as possible in user.clj If you have "dev niceties" over there, prefer a delayed requiring-resolve to a require

And last but not least, it is very customary under clj/emacs/lisp tradition to have repl sessions that last days (weeks, for the most hardcore users) :) Worth the if your workflow is excessively "stateless"

I totally get that a lot of people like to leave REPL sessions running for a very long time, and I used to with smaller projects, I just can't with such a large application, it takes too much memory on my old computer

Thank you though, I'll take a look at the link and see what I can do

👀 how much memory are we talking about?

2-3gb on an 8gb machine

Plus LSP is using an extra 1.5gb of memory

So I just close Emacs entirely

yeah honestly 8gb is peanuts 😅 and running cider and lsp has its cost I'd recommend to use a machine up to the job you're doing - human time is more valuable than material costs :) i.e. it will avoid hacking/headaches.

I don't disagree, I just don't want to dish out for a new computer yet. I've spent too much the past few months as is! 😅