lambda-emacs VS gcmh

You might look at crafted emacs and my own lambda-emacs (not sure if either of these are properly classified as "distros" though). Both default to vanilla Emacs bindings. The repo for lambda-emacs also has a bunch of links to some other great vanilla configs like Prelude, etc.

I am a professor in the humanities (philosophy) and I maintain a framework for Emacs (I don’t know if it rises to the level of “distro”) that is conducive to humanities work, including writing, notes, citations, a good ui, and basic programming. I’m happy to say more if you have any questions. https://github.com/Lambda-Emacs/lambda-emacs

See my lambda-emacs and lambda-themes. They are meant for writing and readability.

7 - Meow: Meow is great. I switched from evil a few months ago and am pretty happy with it. I also dropped general.el for bind-key.el, which is included with use-package (which I see you are using anyway). You can look at my setup of meow here and a more generic setup of keybindings here. I haven't had any trouble with using this instead of general.

cf. https://github.com/emacsmirror/gcmh (the author's [=Andrea Corallo's] Emacs package "GCMH - the Garbage Collector Magic Hack")

A lot of people use way higher values than 800 KB without any problems. As a matter of fact, I've been using 256 MB for a very long time, haven't noticed any issues with it. So I wouldn't call 1 GB madness, it can be perfectly fine in some cases, especially if one uses gcmh, so it has a high chance that GCs will happen when the user doesn't interact with emacs (I also setup emacs to do GC when emacs loses focus. This means that GC pause is invisible most of the time for me). I strongly prefer very rare, short GC pauses than microstuttering all the time. Also, some operations apply a lot of pressure to the memory system, and do hundreds of GCs with the default setting, so most of the CPU time is spent in the GC when these operations run. Increasing gc-cons-threshold makes such operations much faster which means less pauses.

One possible solution is to switch to a LSP approach. You should also take a look at the garbage-collector-magic-hack package: https://github.com/emacsmirror/gcmh

If you experience some lag, my first advice would be to install the GCMH package. It basically changes the garbage-collection rules to ensure that most garbage collection will happen in small bouts while Emacs is idle. After installing it I've never had my Emacs lag on me. This wouldn't address the retina-display issues you mentioned, but I've never experienced those with emacs-plus.

I've seen gcmh recommended as a library that configures the garbage collector for you. Not sure if it is truly a "one size fits all" solution though.

I’d add that for 1) beacon is a good package. For 2), this may be an issue where you have multiple emacs configuration files. This is a serious problem. 3) be patient, and use the magic GC hack. To add to that, you should probably set the GC threshold to be high. 4) projectile? 5)emacs -nw.