I'll stick to an IDE. Modern IDEs are sophiscated enough that a Vim/Emacs newbie user probably needs years of practice and tons of plugins to match and go over its capabilities. I think Vim makes a lot of sense when 1) the machine doesn't have a proper IDE, and 2) you really do a lot of programming every day and you are young, like in 20s, so you can amortize the cost for longer time.
I am making a game. I use Vim (infinitely faster and more product than other text editors) and write a single command in my terminal to compile. Vim makes a lot of sense when you want to work fast and don't want bloated development toolchains to slow you down. There's nothing in modern IDEs that would increase my productivity that I can't add to Vim in about 5-20 minutes.
Vim Creep (2011)
161–169 of 169 posts
Re: Vim Creep (2011)
#162Earlier quoted context omitted.
I am making a game. I use Vim (infinitely faster and more product than other text editors) and write a single command in my terminal to compile. Vim makes a lot of sense when you want to work fast and don't want bloated development toolchains to slow you down. There's nothing in modern IDEs that would increase my productivity that I can't add to Vim in about 5-20 minutes.
Just curious do you plan to open source or sell it? WOuld love to see other's game.
Re: Vim Creep (2011)
#163Earlier quoted context omitted.
Just curious do you plan to open source or sell it? WOuld love to see other's game.
I think I'll have an alpha/beta testing period with interested volunteers. Then hopefully sell it. Then after some years and waning interest, probably open source it.
Re: Vim Creep (2011)
#164Re: Vim Creep (2011)
#165Earlier quoted context omitted.
You clearly have never used a modern IDE.
Is IntelliJ IDEA not modern enough?
There's nothing "mouse-driven" in developing with IDEA. Well, except window/panel management. It is objectively bad.
Re: Vim Creep (2011)
#166Earlier quoted context omitted.
Yeah I always wonder who these people are for which the editor is a bottleneck and how they work or what they work on. 90% of my time is spent debugging, understanding legacy code and drawing trees or writing pseudo code on my notepad. The actual time I type stuff into an editor is like 10minutes per day.
It's not about typing speed, it's about reducing mental load. When vim (or any editor for that matter) becomes second nature, you stop thinking about how you're editing the text, it just happens, like moving a part of you body. And then you can better concentrate on the problem at hand, which matters even more for solving novel problems/algos/architecture. Same with touch typing: you don't need the speed, you need to…
Re: Vim Creep (2011)
#167Earlier quoted context omitted.
Aren't these technically plugins for emacs that are shipped with the editor? Org-mode is a plugin for emacs too right?
Sure but what’s the difference? That’s the beauty (and occasional curse) of Emacs. There’s no hard line between “native” code and plugins, outside of the Emacs Lisp interpreter.
Re: Vim Creep (2011)
#168Earlier quoted context omitted.
My .bashrc is on a quest to turn my yakuake into the better half of vscode. "The shell is my IDE" is definitely true. Though Google takes up a worryingly large fraction of it. Wonder if there could be a shell tool to just dump the first stackoverflow hit for a search. bashrc highlights: https://gist.github.com/FeepingCreature/649588a2f6fa27c717bd... - ctrl-G for "directory up" - ctrl-E for "find and open in editor" (…
> and of course, for german keyboard layout devs, rebinding capslock to alt-gr. I went the other way: use a US layout keyboard, and bind capslock to switch to German layout while capslock is being held down. I find that I need my fancy braces and brackets more than my umlauts. :)
Re: Vim Creep (2011)
#169Earlier quoted context omitted.
I've tried the Vim plugin for VSCode a few times personally, but I don't trust it. It's incomplete, and it has its own secondary understanding of history that can get you into trouble when it interacts poorly with VSCode's own history. Anyway, that was my experience for my short time using it. I'm curious if there are any longtime vim users using VSCode with the Vim plugin, and if so, what are their experiences, and…
I used to, but switched to https://github.com/asvetliakov/vscode-neovim . It's much faster, doesn't lag the editor at all and has less of an impedance mismatch because it uses Neovim under the hood instead of trying to emulate functionality from scratch. There are a few reasons why I use a vim plugin instead of vim proper for most day-day work: 1. I do plenty of data science-y stuff that requires support for good vis…