So very sad to hear about the passing of Ruby legend Jim Weirich
11–20 of 64 posts
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#12A Hacker left us.
R.I.P.
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#13Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#14Very sad to hear. his last commit was only a day ago: https://github.com/jimweirich
he was hacking as usual
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#15Very 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
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#16Very sad to hear. his last commit was only a day ago: https://github.com/jimweirich
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#17http://www.youtube.com/watch?v=FITJMJjASUs This talk is a must-see, really shows off Jim Weirich's craft and overall ability to be a great pedagogue.
Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#18Re: So very sad to hear about the passing of Ruby legend Jim Weirich
#19Just 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,…
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.