Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> 1) Vim and Emacs are already on your production servers so a large number of people have to use them anyway so that's extra mental overhead.

Production servers usually have no vim plugins. Basic vim editing is good enough to get by if you're just looking at logs.

In my workplace and I guess it's pretty standard these days (in Linux shops at least) where the code repository resides on a server in a data center and not locally on your laptop/desktop.

Here are the issues with this development work flow:

- There are a lot of hurdles to go through to install all the vim plugins (no root access, security of plugins etc.)

- Which plugin manager to use (Vundle, pathogen or some variant??). Why isn't there a standard for this after all these years?

- Unreadable .vimrc file with all sorts of key bindings (Yes I know it's "write once use everywhere", it still is unreadable a few months down the line)

- In my experience, using vim on a mounted drive with the plugins I need (git,ctrl-p,ctags,cscope,nerd tree and a few others) is slower as compared to Sublime Text.

> 2) Sublime development is languishing this will eventually lead to a stalled plugin pipeline and the need to learn a new tool or write your own plugins.

https://packagecontrol.io/stats

I don't think these are low numbers by any means.

I'm not a vim basher, I just don't prefer working with it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: