5 ms·
I think you may be overly generous to Emacs. When I use Emacs, it's more I need to go through hundreds of lines of others' Emacs Lisp configurations to figure o
by bmitc 6y ago
I think you may be overly generous to Emacs. When I use Emacs, it's more I need to go through hundreds of lines of others' Emacs Lisp configurations to figure out how to do the thing I want to do or spend many times 5 minutes Googling how to do <x> in Emacs. A good example of this is Elixir's helpful coloring and tab completion in its help documents. When I tried running Iex in an Emacs terminal, it just didn't work, and after Googling, it's just a mess of solutions. It literally just works in Visual Studio Code's terminal.
I forced myself to learn Emacs for a class, and it was really quite painful. I get the power of the bindings and all that, but it's really a mess of an ecosystem, and I encountered plenty of bugs. Even then, I never got things to work just right, and it worked poorly when doing things across Windows and WSL boundaries. Another thing was that any time someone used my Emacs, they couldn't because it wasn't like their Emacs.
So I've just gotten used to Visual Studio Code because I spend more time doing the thing I wanted to do than finding out how to do something simple in the editor. I add a single custom keybinding for toggling between the terminal and the code window, which can now be synced using a Microsoft account. I just install whatever extension I want (through one extension manager) and go at it. Combine this with the extremely powerful and useful extensions of Remote - SSH and Remote - WSL that allow you to use Visual Studio Code on basically any other computer with your extensions as they work on Windows, then you have a one-stop shop for development.
https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview
And by the way, Visual Studio Code can do graphical tasks: https://marketplace.visualstudio.com/items?itemName=hediet.vscode-drawio https://marketplace.visualstudio.com/items?itemName=hediet.v...
Is Visual Studio Code perfect? No. Can someone be more productive in Emacs than Visual Studio Code? Yes, but likely only if they've spent an inordinate amount of time learning Emacs and Emacs Lisp. But Visual Studio Code provides a nice balance of a single environment across languages that evolves with users' needs and basically anyone can be productive in it today.
My personal preference is to use the standard IDE with whatever language I am using, and then to default to Visual Studio Code whenever there is no such standard. I also use a fair amount of visual languages that text editors do not work for.
- alyandon 6y agoAnother thing was that any time someone used my Emacs, they couldn't because it wasn't like their Emacs. You hit the nail on the head. I spent months forcing myself to use nothing but Emacs to get past the "this is unfamiliar and therefore hard" stage. My final conclusion after the experience was that Emacs is pretty powerful out of the box but it is absolutely a general purpose environment and you have to meld it to your own workflow to truly unlock its potential. Even though I don't use Emacs these days, one thing I did keep was swapping capslock and ctrl on my keyboard. That is useful for so many other things and I'm never going back.
- paledot 6y agoI can't speak for Emacs, but just this week I went through my vimrc file and deleted half of the configuration. Turns out now that I've started to grok the finer points of the editor, the heap of cool mappings, functions, and must-have plugins I found on the internet are more hindrance than help.
- jnxx 6y agoAny kind of set-up is done in textual configuration. And this is a major plus. That means you get quickly to see what you have configured, you can put it into version control and check it out on a different machine, and so on. This is a big ergonomical difference to IDEs. As the technical foundation, it is rock-solid. Emacs is based on lisp which has basic text manipulation instructions implemented in native code. This makes it both extremely easy to configure and extend it. It is also from a time when Linux was not yet existant, Unix was not yet universal, and Lisp machines were a thing, so it has a certain platform feeling - while also having good access to the OS. It is certainly possible to use Emacs in text mode as a login shell or as a terminal manager. To that adds another quality of Emacs and vi, one which these IDE enthusiasts can not even understand, which is that the user interface is incredibly stable. And this means that something you have become used to will not change and drift under your feet like quicksand. And in the long run, this really saves a ton of time. That does not mean you can't change things, rather you can change stuff under your control, like using the better-defaults setup.
- jml7c5 6y agoI'm not sure I would consider Emacs's technical foundation rock-solid. Elisp is a bit of a relic, with little in the way of modern niceties, some anti-features, and a slow implementation. And heavy use of cons lists causes a lot of pointer-chasing.
- jnxx 6y agoSo, it might please you to read that there is a slow but steady process to replace elisp by Guile: https://www.emacswiki.org/emacs/GuileEmacs https://www.emacswiki.org/emacs/GuileEmacs And to me, this is a indication of a solid foundation: That you can swap out some base infrastructure for another when you need to, without messing everything up. (Another example is that Racket was switching the core implemenation to be based on Chez scheme, which compiles to native code).
- jml7c5 6y agoIt's possible my information is out of date, but I am under the impression that guile-emacs development stalled five years ago.