bram

Thought experiment: Bram moves to Washington DC, where the air is cleaner than in Delhi, but is instead shot in a mugging gone wrong and permanently confined to a wheelchair.

It is a minor sadness that Bram didn't choose a lisp as the vim macro language.

Vim was created in 1988, but source control wasn't used until 2004 and Bram is the only one with write access.

I could be wrong, but it's unlikely that Bram has had a change of heart regarding encouraging contributions.

Yeah, imagine Bram re-reading this article when he's a brittle 25-year-old whose health is failing while his peers are in their physical primes.

On topic: I find it funny that someone of Bram Cohens' standing would miss the point of fast compilation.

NeoVim has my full attention; it's a forward thinking project that is doing everything I hoped Bram would do.

This is likely due to a combination of Bram being a very busy person and mailing lists being terrible for this sort of thing.

I don't think Bram gets paid to maintain VIM, so you get what you get.

For the few people who have never heard of Bram Cohen or Joe Hewitt (currently 1 and 2 on HN), then their names are just noise.

That was created by vim creator and maintainer Bram himself.

It seems like Bram Cohen made one cool open source project and then sold out as soon as he realized he could get rich off of it.

On Bram's site, using the title "Bram Cohen: Comments on Go" would be redundant.

I don't ever see a response from Bram saying "merged this".

Bram's initial response can be quick, but it's often an ordeal to actually get a patch merged, even for trivial ones.

Bram Cohen, the guy behind the Bittorrent protocol, worked for Valve for a short time.

For stuff that requires feedback from Bram, sometimes there's just no response[3].