i give up now. the problem i have with my neovim plugin cannot be solve with code or documentation.
as long as people think theprimeagen is the absolute source of truth, there's nothing i can do.
@vonheikemen I see, configuring neovim as a IDE is not that easy for a beginner, and its a moving target. But really if one wants to call himself a dev there should be some comitement for solving lua problems.
Anyway don't give up on those tutorials, even for me there is always something to learn new from!
> they don't care about learning the basics
One fundamental difference between VSCode and Vim is that VSCode draws a hard(er) line between "users" and "makers". To configure VSCode, you change some JSON values, to change the editor, you download a big package with node modules and linter configs and switch to "programming mode".
Vim doesn't make that difference. Config *is* programming. You don't "write a plugin", you make simple tools and optionally turn them into a plugin.
@vonheikemen This isn't *bad*. This is just a difference in philosophy. For me, Vim's way has been fantastic. I love being able to hack together small tools that solve small problems, and only when they reach critical mass I think to myself "I could extract this, I guess". For someone who just wants to get work done, I can understand why they wouldn't want to figure out how functions and stuff work in a different language just to set up their basic tools.
@vonheikemen Neovim, I feel, pushes in both directions. The popular perception is that it's more "user-friendly", which to former VSCode users means "simple config". Lua is not that. It's a full-blown general-purpose programming language, where if you miss a comma, the entire file won't load (which is not the case in Vimscript, which is much closer to a "configuration" language).
Lua was meant for makers, just like the RPC tools. But the marketing pushes user-friendliness. They don't mesh.
@vonheikemen If Neovim wants to be the new VSCode, it has to cater to "users" and to "makers" separately. Maybe leaning on editorconfig or something, I don't know. Distributions are always going to be wonky. I don't see a way this could work, since it feels fundamentally at odds with Vim, but it might be possible.
If they just want to be the editor that has better programming tools, that's a valid choice. But it''s not "user-friendly" the way that many people understand it.
@AndrewRadev neovim (as a project) doesn't want to be the new vscode. the impression i get is they know some things are more complex than they should, so there is some work being done to make neovim easier to use. is not going to be a "plug n play ide" anytime soon though.
(funny that you mention editorconfig, neovim v0.9 has support for it, and is enabled by default)
@vonheikemen Sure, I'm just saying that many people trying to use Neovim don't understand just how different Vim is philosophically from "normal" editors. Hence the amount of general confusion.
Videos and guides that say "just do this one trick and you're done" or "just use distribution X" select for people that, as you say, skip steps.
@petrisch lsp-zero.
to be fair, the problem is not just outdated tutorials (like primeagen's 0 to lsp video). but people skipping steps. they don't care about learning the basics, so even the smallest obstacule can cause a lot of confusion. and they trust these tutorials more than the official documentation. it's a whole set of problems.
i saw someone deleting their entire neovim config because they could not figure out a lua syntax error. and they were just missing a comma.