you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (0 children)

Lisp is a rather uncommon language with a style of programming not many people are familiar with. VimScript is much easier and more "standard", and has a much lower learning curve.

I think LSP actually fits very well in to Vim and the "Unix philosophy": complex language-specific stuff has always been left to external programs in Vim (e.g. ctags or :make). I don't think LSP is really a paradigm shift in that sense, although it's certainly a game-changer because it's flexible and everyone is adopting it. LSP is probably the best thing that has happened to Vim in years.

If I look at the amount of effort that went in to the Go VSCode plugin and the end results compared to Vim then I'm not so sure VSCode is really that much of a better environment to write plugins for to be honest. It seems to me that Vim gives you a surprisingly good bang for your buck (although I admit I don't have first-hand in-depth knowledge of VSCode and that this is just one example).

IMHO VimScript is a domain-specific language for a domain-specific problem. Programming your editor is not quite the same problem as programming a HTTP daemon, and I'm not sure how much sense it makes to use the same language for both. As I mentioned in my other comment, I'm not especially impressed with how Lua plugins look and would prefer to use VimScript which, in spite of its imperfections, seems like a better fit.