Bram Moolenaar has died
331–340 of 449 posts
Re: Bram Moolenaar has died
#332RIP, never met him, but I'm a VIM user.
Re: Bram Moolenaar has died
#333Went to his website. There was an interview of him from 2022. The answer that really stroke me was not about Vim, but about software craftmanship vs professional programming: « I have been working for a company where quite a few managers, educated in physics and mechanics, thought the software was just the same as what they knew and they could decide how to make it. That company went downhill and was eventually taken…
I've worked with enough "professional" programmers to know I don't want to work with them and their sloppy, reckless, uncurious, and inconsiderate ways.
So what do you do for a living?
Re: Bram Moolenaar has died
#334No piece of software has influenced my career and my thinking on design, user interfaces, and software quality as much as VIM. VIM made learning to code as fun as playing a game. Thank you Bram, you changed my life.
Re: Bram Moolenaar has died
#335RIP
Re: Bram Moolenaar has died
#336Went to his website. There was an interview of him from 2022. The answer that really stroke me was not about Vim, but about software craftmanship vs professional programming: « I have been working for a company where quite a few managers, educated in physics and mechanics, thought the software was just the same as what they knew and they could decide how to make it. That company went downhill and was eventually taken…
The last sentence was the point. Either end of the spectrum are people who are not caring about the right things (typically about themselves, egos, etc).
Re: Bram Moolenaar has died
#337wq!
he had green squares until his death https://i.imgur.com/MrofIBq.png
Re: Bram Moolenaar has died
#338Earlier quoted context omitted.
I feel it's much more common to create abstractions without regard for performance cost of the abstraction. So keeping time complexity down, even for a piece that doesn't matter much, is above average for this sort of thing.
Also creating abstractions without considering the mental overhead of reasoning about what the code is doing. Not enterprise: event --> action. Enterprise: event --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> action_parta --> abstraction --> abstraction --> abstraction --> action_partb abstraction --> abstraction --> abstraction -->…
I sometimes wonder if people believe that enterprise devs create abstractions for "fun" without having any rational reason.
Re: Bram Moolenaar has died
#339Went to his website. There was an interview of him from 2022. The answer that really stroke me was not about Vim, but about software craftmanship vs professional programming: « I have been working for a company where quite a few managers, educated in physics and mechanics, thought the software was just the same as what they knew and they could decide how to make it. That company went downhill and was eventually taken…
I understand wanting to write beautiful code, it's a major motivator for me. But it does have to actually do something useful - or there's no point.
The code itself, its elegance and cleverness can be a point in itself. I'd argue it's a stupid point (with a few exceptions ala CCC), but for some people it does seem to be the main driver.
Re: Bram Moolenaar has died
#340Such a loss. I've spent many hours reading vim's incredible source code and documentation while developing a vim emulation plugin for the Julia REPL. Absolute world class codebase.
Moolenaar was an amazing programmer, and his impact will be long lasting. May he rest in peace.