Strange that there's no v9.2 tag in https://github.com/vim/vim/tags.
Vim 9.2
21–30 of 203 posts
Re: Vim 9.2
#22I'm glad to see that Vim9 continues to make progress. The center of gravity may have shifted somewhat towards Neovim, but the Neovim ecosystem currently seems targeted towards people who want something more IDE-like. One question is: will more plugin authors move to Vim9Script? It seems that Neovim users have generally moved towards Lua-based plugins, so there's less of a motivation to produce plugins that support bo…
I'm not the target for your question (I distribute 0 plugins). But Lua support in Neovim is the primary reason I moved over from Emacs. Elisp and Vim are both so heart sink for me. That said I'd have preferred something other than Lua if I had the choice.
> That said I'd have preferred something other than Lua if I had the choice.
Same. I know we as a community would never agree on what that language should be, but in my dreams it would have been ruby. Even javascript would have been better for me than Lua.
Re: Vim 9.2
#23But where are the AI features?? Gonna get left behind!
Only joking of course, actually quite refreshing to see a new version announcement of something this major without any AI nonsense.
Re: Vim 9.2
#24Earlier quoted context omitted.
I'm not the target for your question (I distribute 0 plugins). But Lua support in Neovim is the primary reason I moved over from Emacs. Elisp and Vim are both so heart sink for me. That said I'd have preferred something other than Lua if I had the choice.
> That said I'd have preferred something other than Lua if I had the choice. Same. I know we as a community would never agree on what that language should be, but in my dreams it would have been ruby. Even javascript would have been better for me than Lua.
> Even javascript would have been better for me than Lua.
Why?
Re: Vim 9.2
#25Should stop and help with neovim
This is the perennial argument that IMHO is based on a fallacy. If the vim people suddenly stopped working on vim, it doesn't mean all their effort would go to neovim. People work on what they want to work on in open source. Also the two projects have very different goals/philosophies. The code bases have also gotten pretty different in architecture because neovim did a monstrous refactor. It's open source working as intended that we have both.
Re: Vim 9.2
#26Re: Vim 9.2
#27Earlier quoted context omitted.
> That said I'd have preferred something other than Lua if I had the choice. Same. I know we as a community would never agree on what that language should be, but in my dreams it would have been ruby. Even javascript would have been better for me than Lua.
> Even javascript would have been better for me than Lua. Why?
Because I know javascript a lot more than I know Lua (and I suspect given js popularity, a lot of people are in the same boat). Yes Lua is easy to learn, but it's still different enough that there is friction. The differences also aren't just syntactically, it's also libraries/APIs, and more. I also don't have any need/use for Lua beyond neovim, so it's basically having to learn a language specifically for one tool. It's not ideal for me.
But the people who did the work wanted Lua, and I have no problem with that. That's their privilege as the people doing the work. I'm still free to fork it and make ruby or js or whatever (Elixir would be awesome!) first-class.
Re: Vim 9.2
#28Earlier quoted context omitted.
I'm not the target for your question (I distribute 0 plugins). But Lua support in Neovim is the primary reason I moved over from Emacs. Elisp and Vim are both so heart sink for me. That said I'd have preferred something other than Lua if I had the choice.
> That said I'd have preferred something other than Lua if I had the choice. Same. I know we as a community would never agree on what that language should be, but in my dreams it would have been ruby. Even javascript would have been better for me than Lua.
Lua, especially with LuaJIT, is nearly as fast as C. I certainly don't want to have to run a slow language like Ruby or especially a full blown JS runtime like V8 just to run Vim, the entire point is speed and keyboard ergonomics, otherwise just use VSCode.
Re: Vim 9.2
#29Strange that there's no v9.2 tag in https://github.com/vim/vim/tags .
The relevant release commit is, https://github.com/vim/vim/commit/e7e21018fc0b60c153c8e668f6... (at time of writing, two hours ago).
It seems they didn't publish the tag yet though.
Re: Vim 9.2
#30[flagged]
In case you're wondering: I'm not blocked in this thread, but I was blocked in a thread about ICE. I told them to thaw out.
If the thread was deleted by a mod or flagged in the time between starting a comment and hitting "reply", you'd see a message that "you're not allowed to post a comment here" or similar language. Nothing to do with you, it's the state of the thread you're commenting on.