3 ms·
<disclaimer> After using Vim, VSCode and IDEs for many years, only recently have I tried to get seriously into Emacs. I use it for everything nowadays (from org
by rvieira 5y ago
<disclaimer> After using Vim, VSCode and IDEs for many years, only recently have I tried to get seriously into Emacs.
I use it for everything nowadays (from organisation to coding) with the exception of some very large Java projects where IntelliJ is definitely the best option for me.
org-mode was my "gateway". I always wanted to learn Lisp, so I guess that was a plus too (I'm aware Elisp is not the best way to learn it).
</disclaimer>
I don't know if VSCode will be the new Emacs but I doubt it.
It will be, and already is, hugely more popular, and I'm glad it is. I believe in people having a good choice of open source tools and using whatever they feel better using.
What I like about Emacs is that you are given vanilla editor and you have to make it "your own".
Now some people like this, some people hate this. Some people like to quickly download a VSCode extension and just get on with it.
I also like how Emacs' "things" can have a synergy. I just recently setup my blog to be written in org with Jupyter-like code examples, pre-processing and exporting. This involves a few packages but they worked together nicely, It's all text after all.
I don't know how to do that in VSCode (parsing using an extension, processing the result using another, exporting with yet another, etc).
Perhaps it's simple, but I guess that if you are doing this, then between VSCode and Emacs, they both require a reasonable amount of work.
Regarding speed I'm using Emacs 28 native and I feel it's a massive improvement.