Explore >> Select a destination
|
You are here 
|
ncona.com | ||
| | | | |
dusty.phillips.codes
|
|
| | | | | Throughout my career, Ive at least tried most of the available programming editors. More than two decades ago, I heard about the vi-vs-emacs debate, and made a pact with myself to use both for at least a year before deciding which I preferred. I started with vim, switched to emacs after a year, and decided I preferred vim. I joined the sublime-text bandwagon for a year or two in the early 2010s, switched back to vim in the middle of the decade, and eventually did the big switch to vscode. | |
| | | | |
mariocarrion.com
|
|
| | | | | Packer is no longer supported; time to migrate to lazy; also, I decided to stop using vim-go, replacing it with go.nvim | |
| | | | |
sookocheff.com
|
|
| | | | | I first learned Vim in university and, since then, it has been a welcome companion for the majority of my software engineering career. Working with Python and Go programs felt natural with Vim and I was always felt productive. Yet Java was always a different beast. Whenever an opportunity to work with Java came up, I would inevitably try Vim for a while, but fall back to IntelliJ and the IdeaVim plugin to take advantage of the rich language features a full-featured IDE can give you. | |
| | | | |
www.github.com
|
|
| | | my blog, with astro. Contribute to Krayorn/blog development by creating an account on GitHub. | ||
