Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From Vim to Emacs in fourteen days (2015)

blog.aaronbieber.com

Post reply on HN
Print view View original

121–130 of 182 posts

Re: From Vim to Emacs in fourteen days (2015)

#121

Post by kQq9oHeAz6wLLS »

champagnepapi wrote: post #120
joadha wrote: post #114

Earlier quoted context omitted.

Here's the thing, though. I don't use Vim as an IDE. I use it on live servers to change configs / scripts / app code (don't tell anyone) quickly and efficiently. I don't think "extra doodads" would help with that, and I'm not sure I'd want to manage those dependencies on my platform anyway. If I'm actually developing something that's part of a greater whole, then I'm using a fully fledged IDE like PyCharm (but with t…

Changes to PRODUCTION app code on server?! I’ve seen this happen once or twice at my current company. Not the best of times...

Everyone has a test environment. Some are lucky enough to have a separate production environment.

Re: From Vim to Emacs in fourteen days (2015)

#122

Post by poidos »

kirubakaran wrote: post #88
SkyMarshal wrote: post #78

Earlier quoted context omitted.

Fwiw Spacemacs is another good combination of the two, similar to evil mode. https://www.spacemacs.org/

Doom too https://github.com/hlissner/doom-emacs

+1 for Doom. I tried spacemacs for a while but didn't find it enjoyable. Doom was exactly what I needed and now I don't use anything else.

Re: From Vim to Emacs in fourteen days (2015)

#123

Post by cutler »

cwlb wrote: post #65
maximilianroos wrote: post #39

For those who use Vim bindings, and would like to try out emacs, I'd suggest trying Spacemacs: https://www.spacemacs.org/ It has "evil mode" by default — the vim bindings. I picked this up at Jane Street, where much of the internal tooling is in emacs. I still use it wherever I can't get a good vscode setup, and it has some advantages over vscode.

I picked up spacemacs earlier this year but have since switched to Doom emacs: https://github.com/hlissner/doom-emacs it's smaller, faster, and you configure it in a way that's closer to vanilla emacs. The size makes it more tractable to learn. The creator & primary maintainer is more active, funny, and helpful than the spacemacs maintainer who I believe is on hiatus. I wish someone had told Doom about it before I pi…

I've been using Spacemacs for Clojure development for years but stable has been stuck on the same version for ages so is it actually maintained?

Re: From Vim to Emacs in fourteen days (2015)

#124

Post by bern4444 »

alex_smart wrote: post #49
andrewzah wrote: post #24

This article fails to explain -why- one would want to switch to emacs from vim. Org-mode and configuring emacs in a lisp-like are cool, but are not worth re-learning everything for me. I put that time in already by reading "Practical Vim" by Drew Neil and other vim literature online. I'm sure everyone is already aware, but vi is available basically everywhere. This has saved my ass at least twice where I couldn't acc…

How many lines of vimscript have you written? No, copy-pasting config lines from someone's dotfiles doesn't count. How many times have you opened the source code of some vim plugin you are using and tried to modify what it does? If I were to hazard a guess: zero. That was also me during ten years of vim usage. Vim encourages the mindset of mastery = learning a bunch of tricks, remembering them and incorporating them…

The vim landscape today is pretty incredible. Neovim nightly supports native LSP (and Treesitter!) so you get all the functionality that VSCode pioneered.

Neovim also supports configuring your setup in lua, certainly a better language than vimscript (which I agree isn't great) and lets you write native neovim plugins in lua.

Emacs of course supports LSP (and probably treesitter), I'm just reflecting on the fact that (neo)vim continues to evolve.

I think without neovim, vim popularity would have continued to degrade. Though the community, especially with packages like Coc.vim, continues to push vim along and bring support for external features. I personally think neovim is the future over vim given its management and native support for LSP and Treesitter.

In either case, its awesome both editors are still going strong! While VSCode and JetBrains' IDEs are great, they always feel crowded compared to vim. I love that both (neo)vim and emacs still have such large communities behind them. Both are great examples of software that is old, receives improvements and evolves, and continuously delivers value to their users.

Re: From Vim to Emacs in fourteen days (2015)

#125

Post by cylinder714 »

kenbolton wrote: post #55
alfiedotwtf wrote: post #8

I’m curious to hear from folks who have switched between the two, and have lasted for more than a year on both. If you’ve learned more than the basics and both became muscle memory, which did you end up sticking to? (Vim user for 23 years, Emacs user of none... but interested because of Lisp)

Emacs user for the years in college, with the occasional forced dip into vi. Vim user for ten years after college with a couple of forced dips into Eclipse and other IDEs, with vi keybindings where available. Evil emacs user for about the last ten years. Magit makes me happy. Tramp wins the "but vi is everywhere" conversation. Org-mode wins. I won't hire someone unwilling to give emacs an honest effort. Switching bac…

I won't hire someone unwilling to give emacs an honest effort.

An employer has no business dictating what text editor their employees use, if they're productive.

Re: From Vim to Emacs in fourteen days (2015)

#127

Post by ARandomerDude »

ph2082 wrote: post #117
dang wrote: post #2

Just for fun, here are some of the larger past threads. Others? After over a decade of Vim, I’m hooked on Emacs - https://news.ycombinator.com/item?id=16551796 - March 2018 (161 comments) A pragmatic decision on GNU Emacs versus Vim for programming - https://news.ycombinator.com/item?id=13590944 - Feb 2017 (59 comments) Why I switched from Vim to Emacs - https://news.ycombinator.com/item?id=13130775 - Dec 2016 (101 c…

From >> Debian's Vim maintainer switches to Emacs - https://news.ycombinator.com/item?id=341492 - Oct 2008 (32 comments) He warned me I should switch from vi to emacs because prolonged vi usage causes hair loss. :)

Maybe, but prolonged emacs use causes carpal tunnel syndrome!

Re: From Vim to Emacs in fourteen days (2015)

#128

Post by soraminazuki »

joadha wrote: post #114
rtpg wrote: post #106

Earlier quoted context omitted.

I guess, given how evil-mode just gets better and better every day I'm not really seeing many people moving in the other direction, at least based on the blog posts. No shade on Vim, people like it and are productive in it. I see it like using Sublime Text, lots of people can get away with it, but I need more doodads in my editor. And hey, nobody is like "Notepad++ vs. Visual Studio", which I think kinda matches the…

Here's the thing, though. I don't use Vim as an IDE. I use it on live servers to change configs / scripts / app code (don't tell anyone) quickly and efficiently. I don't think "extra doodads" would help with that, and I'm not sure I'd want to manage those dependencies on my platform anyway. If I'm actually developing something that's part of a greater whole, then I'm using a fully fledged IDE like PyCharm (but with t…

Contrary to what many might expect, Emacs tools are quite good for performing sysadmin tasks:

* TRAMP for remote editing. It's more powerful than Vim's netrw remote editing capabilites and can handle root-owned files on remote servers. It's so extensible there's even a package that allows you to edit files inside Docker containers running on remote servers.

* Dired. It's the best text-based file manager out there IMHO, and it integrates very nicely with TRAMP.

* Org mode. It can be used like Jupyter notebook, but is far more powerful. You can write each code block in any language you choose, pass data between them, and make each of them run on different servers. This is very useful for sysadmin tasks especially in professional environments because it allows you to document each step in a reproducible manner as you're executing it. You can then just share the org document for your cowokers to review.

I personally use Vim for coding and Emacs for non-trivial sysadmin tasks.

Re: From Vim to Emacs in fourteen days (2015)

#129

Post by years3500 »

BeetleB wrote: post #98
jimbokun wrote: post #59

Earlier quoted context omitted.

> Vim vs. Emacs is a sideshow at best. Until you need to ssh into a server and edit something.

It's funny you mention that. https://www.murilopereira.com/how-to-open-a-file-in-emacs/ The summary is that the author tried to open a remote file and Emacs froze for several seconds. He dived deep into finding out why that was and how to fix it, pointing out how great Emacs's introspection is that one can find solutions to problems like these. And then two thirds of the way into his essay, he has this: > More recent…

Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish.

https://news.ycombinator.com/item?id=25719338

Post reply on HN