3 ms·

Author instead of looking how to solve this particular issue in emacs threw everything away and tried a glorified browser masked as IDE :)) What I have to ackn

Author instead of looking how to solve this particular issue in emacs threw everything away and tried a glorified browser masked as IDE :)) What I have to acknowledge though is that out of the box experience of VScode is like a billion times better than what you can get with emacs or spacemas. I am not sure about extensibility but I think in the long run VSCode/Atom will greatly benefit from using a language that's just simply more popular. I'll probably stop using emacs when people stop developing great modes for it. I still hate that out of the box experience (even for installing and activating the pkgs) on emacs is a thing from the past.

terminalcommand 9y ago
IMHO out of the box experience does not matter that much from a point-on, because configuring emacs with an existing configuration is very easy. You just need to save your .emacs.d folder and every config you've accumulated over years is there. The nice thing about emacs is the extensibility, you can very easily write your own modules load it etc. I understand the same argument could be made for VS Code, but I think emacs is here to stay, because Electron can never be as responsive as a native application. On the other hand it's true that installing emacs packages and getting them working is cumbersome. Maybe, as a community, we need to prepare modular dot files. For example, are you a Go developer, go install Go Emacs. Or are you a web developer Go install Web Emacs etc. Having a set of prewritten configs would benefit Emacs's popularity. For example my init.el in .emacs.d consists of a couple of lines loading my modules: (package-initialize) (load-file "~/.emacs.d/melpa.el") (load-file "~/.emacs.d/golang.el") (load-file "~/.emacs.d/readability.el") (I see now that there are some prepared configs such as https://github.com/purcell/emacs.d https://github.com/purcell/emacs.d)

terminalcommand 9y ago

IMHO out of the box experience does not matter that much from a point-on, because configuring emacs with an existing configuration is very easy. You just need to save your .emacs.d folder and every config you've accumulated over years is there. The nice thing about emacs is the extensibility, you can very easily write your own modules load it etc. I understand the same argument could be made for VS Code, but I think emacs is here to stay, because Electron can never be as responsive as a native application. On the other hand it's true that installing emacs packages and getting them working is cumbersome. Maybe, as a community, we need to prepare modular dot files. For example, are you a Go developer, go install Go Emacs. Or are you a web developer Go install Web Emacs etc. Having a set of prewritten configs would benefit Emacs's popularity. For example my init.el in .emacs.d consists of a couple of lines loading my modules: (package-initialize) (load-file "~/.emacs.d/melpa.el") (load-file "~/.emacs.d/golang.el") (load-file "~/.emacs.d/readability.el") (I see now that there are some prepared configs such as https://github.com/purcell/emacs.d https://github.com/purcell/emacs.d)