Emacs is a great piece of software. It is highly extensible. Whenever I see someone starting off directly with Spacemacs or Portacle, I feel that an important opportunity to appreciate the extensibility of Emacs is being missed. I have a similar gripe towards the current state of Java programming when I see young engineers starting off with Eclipse or IntelliJ without appreciating how to compile and run programs using the javac and java command line programs. It often bites them back when they have to troubleshoot the program on a production system where there is no IDE and they can only see very long arguments to "java -cp". But I digress here.
My hope with a project like this is that it will help in reducing the allure of readymade fully customized Emacs distributions to some extent and encourage hacking on Emacs itself to customize it to one's own needs, taste, and preferences.
I also think you are right. I am very grateful I managed to get a preconfigured Emacs to start my journey.
This is, in my opinion, the best way to introduce people to light .emacs configuration. To the point that I think there should be 4 or 5 different minimal .emacs such as this one in the main project page.
I understand why there is resistance to enhance the default UX and configuration, and I see the allure of spacemacs, doom, prelude, etc. But it is overkill, and pushes you down a configuration slippery slope that some enjoy too much and others dread, but that kills productivity.
> you learnt that it recommends Emacs and SLIME for development environment and it seemed like a significant additional learning curve for you?
This is the key. This is what pushes a lot of people away from emacs. Just have a "1 click" better default that also serves as a tutorial / example of how to cover 1 simple use case: one for common lisp, another one for clojure, a couple of different ones for python, one for writing a book. Just feed the space between no config and 3h of research. Have something to point out to newbies.