Earlier quoted context omitted.
fd sounds much worse as now you can't jump to d characters.
False. The fd mapping would only apply in insert mode. Jumping to d only occurs in normal mode.
Oops - you're correct, of course.
LazyVim
351–360 of 537 posts
Re: LazyVim
#352I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
I dont know..
The argument i read all the time is "i don't want to invest time in vim".
But what kind of professional spends hours uppon hours learning his craft (programming), but is unwilling to invest some of those hours into mastering professional tools?
What about sharpening the axe? The amount of time i saved by sticking to vim is definitly more that the time i needed to learn it..
IDEs are easy mode and waste of resources.
Its ok to start with them as a noob, but down the line i want to customize every part of my toolchain. (And thats just horrible to do in VSCode etc..)
Re: LazyVim
#353Earlier quoted context omitted.
a colleague of mine answered the same question with: "jetbrains products reek of java" which i translated to "cluttered ui" and "not responsive".
JetBrains product has always been fast for me, as I wouldn't run them on a 10-year-old computer with an HDD drive. They've been very configurable, more than other IDEs I've used. An IDE is a host of tools, so the UI can be dense because they can do so much stuff. You invest in your tools, and that can also mean buying a powerful enough computer to do the stuff you want.
i share your feelings and i'm a happy jetbrains customer (and i dont do java!); but i see the point of people not feeling comfortable using them specially when coming from more pared-down experiences. emacs and neovim are also snappier, vscode is marginally snappier, doesn't bother me but it's noticeable.
JB also has some glaring holes, like the inability of easily specifying an env file to load when running projects from the IDE runner (and the plugin to do this was half broken with the 2023 versions)
Re: LazyVim
#354Earlier quoted context omitted.
> The amount of work needed to get a basic IDE up and running for your languages of choice, I don't think vim is meant to be an IDE. If you want an IDE, go get an IDE. If you want a text editor, vim works well. But vscode is unwieldy as a text editor, and vim is painful to contort into an IDE.
on the other hand, using vim mode in vscode let you use vim where it shines: modal editing. It's the best of both worlds.
not really..
vim is easy to extend and adapt.
You loose that with only vim mode in vscode.
You also loose the ecosystem and relevant core functionality like most vim core functionality like :grep :vim :make, quickfix list, arglist etc..
Re: LazyVim
#355I just open a file stream and write the hex straight to the storage device. Anything else is cheating.
Re: LazyVim
#356Earlier quoted context omitted.
Interesting tip too! Need to find the right combination however, I noticed that Alt-L might be a good one (no side effect it seems).
That will move your cursor to the right by one character after exiting insert mode.
Entering + exiting insert mode with i and Esc moves your cursor to the left by one, so I suppose this neutralizes it?
Re: LazyVim
#357Earlier quoted context omitted.
If you want IDE like features, then of course an IDE is a better choice. I've never understood why people and to extend vim to try to make it half of an IDE.
a colleague of mine answered the same question with: "jetbrains products reek of java" which i translated to "cluttered ui" and "not responsive".
The 'New UI' in PyCharm 2023 is pretty nice. Less of an airplane cockpit vibe. Its still a total hog of compute resources but I have an M1 machine and never notice any problems.
Re: LazyVim
#358I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
This. As someone now in their 30s who didn't learn to code until their 20s, I've tried several times with vim/emacs but it just isn't worth the hassle because I just don't have the free time anymore to endlessly fuck about with config files and learning the ins and outs of each program. So many of the absolute best seem to use one of vim/emacs but then so many of the absolute best started coding when they were childr…
hmm.. but you also spent a lot of time to learn programming. Why not invest some time in the use of professional tools?
If you master an editor like vim, you'll never need to spend time to learn additional IDEs. In the past i needed to learn VSCode, Eclipse, IntelliJ, XCode, Visual Studio and some other niche IDEs. All have very different menu structures and keybinds. Just to unify that was worth the time learning vim.
Re: LazyVim
#359I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing. The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to sp…
> I don't like being sucked back into the Microsoft ecosystem You’re not though, there’s no lock-in.
but there is.
VSCode core may be open source, but the plugin marketplace certainly isn't.
So if you for example use VSCodium, you don't have access to the plugin marketplace and eather have to use an alternative or manage your plugins completely manually on the filesystem.