VulcanSphere@kbin.social to Technology@lemmy.world · edit-21 year agoRIP Bram Moolenaar, the author of vim text editorgroups.google.comexternal-linkmessage-square63fedilinkarrow-up1998arrow-down113file-textcross-posted to: linux@lemmy.mlleftistunix@lemmygrad.mltechnology@beehaw.orglinux@lemmy.mltechnews@radiation.partyopensource@lemmy.mlhackernews@lemmy.smeargle.fanshackernews@derp.foofoss@beehaw.org
arrow-up1985arrow-down1external-linkRIP Bram Moolenaar, the author of vim text editorgroups.google.comVulcanSphere@kbin.social to Technology@lemmy.world · edit-21 year agomessage-square63fedilinkfile-textcross-posted to: linux@lemmy.mlleftistunix@lemmygrad.mltechnology@beehaw.orglinux@lemmy.mltechnews@radiation.partyopensource@lemmy.mlhackernews@lemmy.smeargle.fanshackernews@derp.foofoss@beehaw.org
minus-squaretun@lemmy.worldlinkfedilinkEnglisharrow-up48arrow-down1·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-squarekittenbridgeasteroid@discuss.tchncs.delinkfedilinkEnglisharrow-up3arrow-down70·1 year agoOr we could all just move to nano and be less frustrated.
minus-squarePanja@lemmy.worldlinkfedilinkEnglisharrow-up25arrow-down3·1 year agoDamn people here really hate nano 😂
minus-squaremarkstos@lemmy.worldlinkfedilinkEnglisharrow-up42·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-squarehavokdj@lemmy.worldlinkfedilinkEnglisharrow-up11arrow-down1·1 year agoNah I’ll pass on that, nano feels dirty.
minus-squaresin_free_for_00_days@sopuli.xyzlinkfedilinkEnglisharrow-up5·1 year agoI’m rarely as frustrated as when something opens with nano when I’m expecting Vim.
minus-squareWhiskyTangoFoxtrot@lemmy.worldlinkfedilinkEnglisharrow-up1arrow-down2·1 year agoed is the standard text editor.
minus-squarePanja@lemmy.worldlinkfedilinkEnglisharrow-up3arrow-down6·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-squaretun@lemmy.worldlinkfedilinkEnglisharrow-up21·1 year agoI started with nano, learnt vim and now using neovim.
minus-squarelawrence@lemmy.worldlinkfedilinkEnglisharrow-up2·1 year agoI am waiting for neovim 1.0, using vim until there.
minus-squaretun@lemmy.worldlinkfedilinkEnglisharrow-up4·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.