Should you nvim, btw
I can't stand using VSCode so I wrote my own
161–170 of 186 posts
Re: I can't stand using VSCode so I wrote my own
#162Should use nvim, btw
Re: I can't stand using VSCode so I wrote my own
#163As an alternative to VSCode, consider Theia[1].
Open-source, runs all the VSCode extensions, etc.
Re: I can't stand using VSCode so I wrote my own
#164As an alternative to VSCode, consider Theia[1]. Open-source, runs all the VSCode extensions, etc. [1] https://theia-ide.org
That's the one that took the Monaco editor (the part of VS code originally made by Microsoft) and then advertised it as the true alternative to VS Code.
Re: I can't stand using VSCode so I wrote my own
#165The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…
Just a thought that sometimes people developing C# since the early 2000s don’t come from an open source culture, so fixing bugs in someone else’s programs doesn’t appear in their default list of resolutions.
Best time to learn was 10 years ago, the second best time to learn (and add it to their default list) is today!
Re: I can't stand using VSCode so I wrote my own
#166Or just use Vim. Not sure I understand the obsession with VSCode.
Have you had a good debugging experience with (neo)vim? I'm the author
It's not ideal for me yet. I've had some problems with DAP. The DAP servers I've checked were a bit unstable and slow. For now I'm using gdb with nvim-gdb https://github.com/sakhnik/nvim-gdb
Very reliable and as fast as gdb is. But with all the problems just using gdb has.
Re: I can't stand using VSCode so I wrote my own
#167Earlier quoted context omitted.
That’s why I ask actually. Whats the generally accepted legal interpretation for “personal use”.
I wonder, does it even matter? Who would know what editor you used to write a piece of code?
Unless the author has the significant resources to audit any companies he's suspicious of, no one will know.
Re: I can't stand using VSCode so I wrote my own
#168Or just use Vim. Not sure I understand the obsession with VSCode.
When you use the word "just," you seem to be implying that Vim is a suitable development environment out the box, when in reality it takes hours of configuration over weeks of time, conservatively. Even then it's not going to supplant VSCode or JetBrains for most people due to its limitations.
there are out of the box neovim experiences, like kickstart.vim. I've kept it largely the same, tweaking only small settings like colorscheme, some line wrapping stuff, like I would in any editor.
You really dont have to take hours to install and tweak and debug 100 plugins anymore, if you dont want to
Re: I can't stand using VSCode so I wrote my own
#169Or just use Vim. Not sure I understand the obsession with VSCode.
When you use the word "just," you seem to be implying that Vim is a suitable development environment out the box, when in reality it takes hours of configuration over weeks of time, conservatively. Even then it's not going to supplant VSCode or JetBrains for most people due to its limitations.
It’s likely more “out of the box” than developing your own text editor from scratch.