983
RIP Bram Moolenaar, the author of vim text editor
(groups.google.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2023
983 points (98.7% liked)
Technology
60130 readers
2782 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
RIP, Mr. Bram Moolenaar.
Thank you for the VIM.
Now the time has come for the VIM future.
https://joshtronic.com/2018/08/12/will-vim-die-with-bram-moolenaar/
Or we could all just move to nano and be less frustrated.
Damn people here really hate nano 😂
Na, it’s just that a memorial post is a time to pause the editor wars, if only for a moment, and pay respect.
Nah I'll pass on that, nano feels dirty.
I'm rarely as frustrated as when something opens with
nanowhen I'm expectingVim.ed is the standard text editor.
I mean it was on a response with a link detailing the single threaded nature of vim development.. I don't think it was inappropriate
I started with nano, learnt vim and now using neovim.
I am waiting for neovim 1.0, using vim until there.
Neovim is stable even though it is still using minor version number.
The eco system booms after 0.5 (lua support, lsp and treesitter) and after lazy.nvim.