Live data from Hacker News

So very sad to hear about the passing of Ruby legend Jim Weirich

twitter.com

11–20 of 64 posts

Re: So very sad to hear about the passing of Ruby legend Jim Weirich

#15

Very sad to hear. his last commit was only a day ago: https://github.com/jimweirich

Someone spoke to him just yesterday http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_cre... he was hacking as usual

He seemed to really get into drones and copters whole heartedly over the past year and appeared to be having a lot of fun with it :-)

Re: So very sad to hear about the passing of Ruby legend Jim Weirich

#18
I met him at BigRuby in Dallas, he was kind, knowledgeable, and incredibly intelligent. He was interested in a very wide range of things, and I really enjoyed discussing metallurgy, blacksmithing, controlling drones, ruby, amongst other things. He was always willing to help, even if the problem was beneath him. Rest In Peace Jim, you will be sorely missed.

Re: So very sad to hear about the passing of Ruby legend Jim Weirich

#19
post #8

Just realised how often when working on some code I will try to contact the original author based on git blame... but in the future, a lot of those people won't be around anymore. I think we usually take for granted that people working on the same project will be here - but in a couple of years "anyone who worked on this module still alive?" may be depressingly more common. Not even from the development perspective,…

Not to detract from the work that this man (or anyone else) has done, but it's very rare for code to survive for very long without an active maintainer before it succumbs to code rot.

Either someone else steps up to the plate and actively maintains the software, or something else will replace it. Source control makes it easier to revisit the past, but it doesn't ensure that the past will continue to stay current.

Post reply on HN