151–160 of 203 posts
Earlier quoted context omitted.
I just learned that he passed from Wikipedia. I remember he used to get a lot of flak on HN for not wanting to update vim, back in the days.
Well, it works really well, most of us don't need any fancy new features, and we certainly don't want anything breaking.
But 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.
But 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.
Wayland support for a terminal editor? Woot?
Earlier 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.
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.
As a die-hard vim fan, I feel bitter-sour saying that I switched to nvim. Honestly, I think the vim maintainers should find a way to merge in nvim.
NeoVim tossed significant amounts of legacy code (eg 8.3 filename support) and greatly improved out of the box default configuration. You cannot merge the two without upsetting one camp or the other. Vim wants to continue to be a stable platform that runs on 40 year old hardware. NeoVIM wanted to ditch the cruft that no longer makes applies.
Earlier quoted context omitted.
How many people don’t know tmux in the industry is really beyond me.
What's the elevator pitch if I already know Screen and I can just open multiple windows of the terminal emulator?
As a die-hard vim fan, I feel bitter-sour saying that I switched to nvim. Honestly, I think the vim maintainers should find a way to merge in nvim.
I have also switched to nvim, but every release I consider moving back. Honestly a lot of this is that I hate Lua. With so much of the infrastructure moving in that direction it's basically unavoidable. XDG support was honestly one of the things holding me back; I'm glad that this is finally fixed.
Earlier quoted context omitted.
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.
You don't need V8 for running JS for scripting, you have quickjs[1] or mquickjs[2] for example. You might have problems importing npm packages, but as we can see from lua plugins you don't even need support for package managers. Performance is not as good as luajit, but it is good enough [1]: https://bellard.org/quickjs/ [2]: https://github.com/bellard/mquickjs
Earlier quoted context omitted.
> 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.…