3 ms·
I've been using vi since 1985, built a suite of development tools based on a custom fork of Elvis in the 90's and have been using vim professionally since the m
by Ensorceled 5y ago
I've been using vi since 1985, built a suite of development tools based on a custom fork of Elvis in the 90's and have been using vim professionally since the mid 90's. I've dabbled with emacs on and off for most of the 80's and 90's, including supporting a subset of the Elvis tools on emacs. I still fire up emacs now and then to see what's up.
The idea that either emacs or vim are a "0 fiddling" drop in replacement for Goland or Pycharm is ludicrous. I probably could get vim up to the point where I was as productive as I am with Goland/PyCharm but it would definitely NOT be a "0 fiddling" process.
I can't believe debugging and learning a new code base would be ANYWHERE as easy with vim as with Goland/PyCharm.
Also, both Goland and PyCharm have pretty good vim plugins so my day to day editing IS vim. Sometimes I hit stuff that I can do faster in actual vim and I switch over.
- abzug 5y agoHonest question from someone who never used any product from JetBrains: what those IDEs gives you in order to learn/debug a new codebase in such easy way?
- lordgrenville 5y agoNot OP but having used both PyCharm and Emacs, I really like PyCharm's visual debugging - when at a breakpoint you can see all variables in memory, their types, dictionaries and objects are nested. A lot easier than vanilla pdb.