5 ms·
Before you get all smug, Vim people, this applies just as much to you as to us. :P I'll probably never let go of Emacs, but have encouraged both of my kids to
by tptacek 3y ago
Before you get all smug, Vim people, this applies just as much to you as to us. :P
I'll probably never let go of Emacs, but have encouraged both of my kids to avoid it and use VSCode instead.
- Derbasti 3y agoI've taught programming at the university for a decade. There would always come the time when students would ask what text editor to use. This was an interesting and varied question for many years. But nowadays, it's just VSCode. It may not be open source, and it may not be a particularly exciting (or good?) text editor. But it has become so ubiquitous that I'd just short-change my students if I recommended anything else. They'd still occasionally see me type into my Emacs (which looks nothing like stock Emacs). And sometimes it would even get a kid or two interested. Some even switched to Emacs because of those classes. I have since given up teaching, though.
- sureglymop 3y agoI would, however, encourage anyone to learn the GNU readline keyboard shortcuts. I don't use emacs but I think they are emacs adjacent. I've come across those shortcuts in many many places (that used readline or not). There's also rlwrap which wraps any non readline REPL.
- fragmede 3y agohttps://discuss.kakoune.com/uploads/default/original/1X/f458d8dbc5a45a7e520267b9cf9f066e1d9d4cba.png https://discuss.kakoune.com/uploads/default/original/1X/f458...
- baq 3y agoI've jumped ship from vim to vscode ~5 years ago, for better or worse, after having been a vim person for previous ~20. There are still things I miss which are impossible to replicate in vscode without breaking it, but I feel the out of the box experience and reduction in configuration complexity is a rather large net positive. vim is still what I use to edit stuff via ssh and in docker images, though.
- fragmede 3y agoI wouldn't say I've jumped ship, simply because I'm still using both. I've got vim in a terminal and a vscode window up, and it's not seamless, but I wield the two together to get the job done. Debugging is done in vscode, but vscode doesn't have all the vim stuff in, so in still attached there, plus it runs in a terminal and vscode doesn't.
- lll-o-lll 3y agoDo you use one of the vim plugins in vscode?
- baq 3y agoI tried and they kinda sorta 95% work, but then you hit the missing motions or a keybinding conflict or some extension issue and it’s either fight the thing or go the opinionated way.
- globular-toast 3y agoI've been using Emacs for as long as the author and I've also never really recommended it to anyone. I've never met anyone I could imagine going through with it. I feel like if you're the type to use Emacs you'll find Emacs yourself.
- adamc 3y agoI think that's probably true. You have to dig to see what's good about Emacs, and to get past the initial "this is so alien" impression.
- orbital-decay 3y agoI don't think it applies. Vi's key idea is a composable text editing language, and it's transferrable between editors, with a few quirks but mostly intact. (although there are new editors that iterate on this idea, and they have their own, better designed, but incompatible text editing languages). Emacs' key idea is a composable environment, which translates poorly to non-LISP languages and other programmable editors due to their more rigid design. It's really an operating system with a non-conventional architecture.
- Bjartr 3y agoAs the joke goes: Emacs is a great OS, only lacking a decent text editor