VulcanSphere to Technology • edit-21 year agoRIP Bram Moolenaar, the author of vim text editorgroups.google.commessage-square59fedilinkarrow-up1999arrow-down114file-textcross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
arrow-up1985arrow-down1external-linkRIP Bram Moolenaar, the author of vim text editorgroups.google.comVulcanSphere to Technology • edit-21 year agomessage-square59fedilinkfile-textcross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
minus-square@tunlinkEnglish47•1 year agoRIP, 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/
minus-square@[email protected]linkfedilinkEnglish-67•1 year agoOr we could all just move to nano and be less frustrated.
minus-square@markstoslinkEnglish42•1 year agoNa, it’s just that a memorial post is a time to pause the editor wars, if only for a moment, and pay respect.
minus-square@[email protected]linkfedilinkEnglish5•1 year agoI’m rarely as frustrated as when something opens with nano when I’m expecting Vim.
minus-squarePanjalinkEnglish-3•1 year agoI mean it was on a response with a link detailing the single threaded nature of vim development… I don’t think it was inappropriate
minus-square@tunlinkEnglish4•1 year agoNeovim 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.
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.