4 ms·
I have nothing against VSCode but I don’t use it. For small files and quick edits i use neovim with no customisation at all. Back when I first started using vi
by 57473m3n7Fur7h3 1y ago
I have nothing against VSCode but I don’t use it.
For small files and quick edits i use neovim with no customisation at all. Back when I first started using vim I had a pretty long config and some plugins installed and so on. But now that I no longer try to use it as an IDE, neovim is perfect for small edits.
For development work I use JetBrains suite of tools. Very minimal amount of customisation there also, only a couple of extra plugins installed by me and a couple of changes in the settings. It works well enough that I don’t have any desire to spend time customising it a whole bunch.
- lvl155 1y agoDon’t get me wrong, I loved neovim and other tools but tbh I just nano for simple edits now. AI tab complete is just too good. Basically it’s barebones or VSCode (or its variants). I could probably use vanilla neovim instead of nano but I've not used vim all that much recently to be in that "flow".
- pyman 1y agoThis is like saying: I can write Swift code using Vim instead of Xcode. Yeah, you can, but that doesn’t mean you should. Note: I use nano/vim daily to read and edit files on my servers. Just not to build complex apps.
- rescripting 1y agoYour point is good, I don't mean to undermine it, but because I work in this area I feel compelled to point out that depending on the type of Swift you're writing using NeoVim to write Swift is actually quite pleasant: https://www.swift.org/documentation/articles/zero-to-swift-nvim.html https://www.swift.org/documentation/articles/zero-to-swift-n...
- pyman 1y agoI'm hoping one day to move from a GUI to a VUI (Voice User Interface), though I still have a soft spot for TUIs. Thanks for the link :)