At the level of "Having to configure something to use it", they're the same, but then that's the same as the hundreds of other config options then. I think we can be slightly more precise than that.
In Neovim the choice of language server and the choice of LLM is up to the user, (possibly even the choice of this API, I believe, having only skimmed the PR) while both of those choices are baked in to XCode, so they're not the same thing.
That's fair enough, but it's the opposite complaint, that XCode's LLM support is more limited because it is proprietary. That's a perfectly valid and reasonable objection, of course.
Neovim already supports LSP servers. The fact that a language server exists for anything, doesn't make neovim (or any other editor) "support" the technology. It doesn't, what it does support is LSP, and it doesn't and couldn't care less what language/slop the LSP is working with.
That’s not really native support for LLMs? It’s supporting some LSP feature for completions.
LSP != LLM
You have to enable it and install a language server, that's not the same as an LLM being baked in.
It’s not baked in, in that sense. You still have to enable it in XCode and link it to a Claude account. It’s basically the same.
At the level of "Having to configure something to use it", they're the same, but then that's the same as the hundreds of other config options then. I think we can be slightly more precise than that.
In Neovim the choice of language server and the choice of LLM is up to the user, (possibly even the choice of this API, I believe, having only skimmed the PR) while both of those choices are baked in to XCode, so they're not the same thing.
That's fair enough, but it's the opposite complaint, that XCode's LLM support is more limited because it is proprietary. That's a perfectly valid and reasonable objection, of course.
Neovim already supports LSP servers. The fact that a language server exists for anything, doesn't make neovim (or any other editor) "support" the technology. It doesn't, what it does support is LSP, and it doesn't and couldn't care less what language/slop the LSP is working with.