4 ms·
Notepad++ or SciTE have no support for LSP, tree-sitter parsers or the new debug adapter protocol, which are table-stakes requirements for serious development n
by zozbot234 4y ago
Notepad++ or SciTE have no support for LSP, tree-sitter parsers or the new debug adapter protocol, which are table-stakes requirements for serious development nowadays. So you're pretty much limited to quick and dirty editing of single-file scripts or configs. Meanwhile both Neovim and emacs are getting support for this stuff.
- userbinator 4y agoI do Win32 development almost exclusively using regular Notepad (not even the ++). IMHO codebases that nearly require the use of complex tools to work with are a bad thing as they may contain lots of unnecessary complexity, and the accompanying probability of bugs.
- kalekold 4y agoPlease stop mentioning neovim as if it's a defacto replacement for vim. The original vim is very much alive and much more popular than neovim. Neovim is a cash grab by developers who forked the repo and demanded patreon payments etc. with wild claims that it will replace vim. Neovim doesn't support vim's development it only takes from it. It never pushes anything back upstream and most importantly, never contributes to Bram's charity, ICCF Holland.
- kelnos 4y ago> demanded patreon payments etc. I've been using neovim for years and have never heard of this, and have never paid them anything. I'm not saying you're incorrect that they've asked ("demanded" feels a bit strong?) for patreon payments or other forms of compensation, but a) that is their prerogative, and b) as a user, I haven't felt pressured into contributing at all. > Neovim doesn't support vim's development it only takes from it. It never pushes anything back upstream I suspect at this point they've diverged enough that doing so would be infeasible. And yes, by definition, a fork "takes" from the original parent project. Neovim is not obligated (legally or morally) to contribute back to vim. That's the -- brilliant -- nature of open source & permissive licensing. > ... and most importantly, never contributes to Bram's charity, ICCF Holland. Why is this a requirement? I'd been using vim for at least a decade prior to switching to neovim, and never donated. I think charitable donations are a very personal thing; people can donate to whatever causes they feel like, and pressuring someone to donate to a charity just because it's linked to a piece of software they use (or have forked from) sounds awfully similar in tone to your "demanded patreon payments" rant above. > Please stop mentioning neovim as if it's a defacto replacement for vim. I don't think the GP was trying to do that. They merely pointed out that neovim (and emacs) has built-in support for LSP (etc.), which I believe vim does not? So vim isn't really relevant to the point being made. I think perhaps you should step back a little and ask yourself why this topic seems to be so emotionally charged for you. It's just a text editor; let people use and promote whatever editor they like.
- soupbowl 4y agoThe Neovim community and developers push a lot of things back into vim. Your hate is irrational.
- stonogo 4y agoYou might be in a bubble. Only about a quarter of the developers I work with know of or care about LSP or the debug adapter protocol, and about half of those who do regard them as Microsoft-specific. Tree-sitter is just a personal preference, there are plenty of alternate solutions that work just as well.
- wink 4y agoI don't use any of the scintilla-based editors for serious developments, but as lightweight text editors. I don't even want those two use cases to have the same history for files opened. In fact Notepad++ on Windows is my eternal scratchpad and I open a "code" file maybe once a month.