To further this... Adding packages in emacs are not that hard. The only area (in my opinion) where you have a point are newcommers to emacs. The learning curv

To further this... Adding packages in emacs are not that hard. The only area (in my opinion) where you have a point are newcommers to emacs. The learning curve is as steep as you want it to be. You do need to invest time to understand it and get really good at it. The key combinations, packages, etc. This is likely where many will just go to Visual Studio Code or something else. Emacs... when you take the time to invest, the rewards are HUGE and goes beyond (the likes of) Visual Studio Code. I consider myself an experienced emacs user. Are their better, more talented, absolute beast-like emacs users out there? Yes. More gifted than me? Absolutely. I know enough elisp to get things done quickly. If I needed to put together a new emacs install from scratch, I could get all the main bits I need in 20 mins or less. Better news is my emacs config. Makes use of use-package and factors in Windows and Linux. Nice and clean elisp code!! I can take it wherever and use it for new installs. My comments is not forcing people to use emacs. Can I be bias at times? Absolutely! Do I like a little light-hearted jokes about editors? Absolutely! I use to have a little poke at vim devs in the past. They did it back. We actually learned from each others methods of 'doing something' on our editors. I miss that. I am not religious to emacs but, as software goes, it is close to me. However, I am also open to something replacing it. None of the IDEs or editors available are nowhere near being a replacement... for me. Does not mean something in the future cannot break that mold.