I will start with the bold statement that Emacs configuration is almost the same as system configuration… It's more about Emacs being integrated with so many tools inside the environment.
I believe Twitter:@andrewtropin has really hit the nail on the head with his statement of the problem. This is the crux of the Emacs adoption problem.
Is one variant of the solution not simply Dockerfiles? Also, if licensed under MIT/BSD/Apache it could diffuse into the corporate world. By "simply Dockerfiles" I'm thinking about a preconfig'd Emacs "compute appliance" container, possibly on localhost. On init, start Emacs as server and network to any data to be edited. Then essentially just ssh in.
Such builds would be a painless way for someone to try an Emacs setup.
JohnTigue
commented
3 years ago
This feels like it will be very important for the Emacs world:
EmacsConf 2020 - 08 - Building reproducible Emacs - Andrew Tropin (abcdw)
I believe Twitter:@andrewtropin has really hit the nail on the head with his statement of the problem. This is the crux of the Emacs adoption problem.
Is one variant of the solution not simply Dockerfiles? Also, if licensed under MIT/BSD/Apache it could diffuse into the corporate world. By "simply Dockerfiles" I'm thinking about a preconfig'd Emacs "compute appliance" container, possibly on localhost. On init, start Emacs as server and network to any data to be edited. Then essentially just ssh in.
Such builds would be a painless way for someone to try an Emacs setup.