Jim Weirich, Creator of Rake, Has Passed Away
SirLurksAlot writes "News is beginning to circulate on Twitter and various sites that Jim Weirich, the creator of Rake, has passed away at the age of 58. He was an active developer (his last commit in the last 24 hours) and has made many contributions to the Ruby community over the years, as well as being a prolific speaker and teacher. He had a great sense of humor and was beloved by many. He will be greatly missed."
WTF is "Rake" and why should anyone care? I gather it's some sort of Ruby thing, but again, why should anyone care?
Because Make sucks...
It's cool that he was still coding right up until his death, but that death was much too early.
Based on the Wikipedia photo It looks like he spent too much time improving his mind, and not enough taking care of his body.
If you look like Jim, it's time to change your diet and get active if you want a long healthy life. Tech like FitBit and Jawbone can help. Active gaming using Kinect instead of sitting with a controller, and spending 30 min a day weightlifting did wonders for me.
You'll feel better, think more clearly, and get positive attention from the opposite sex.
I was taken aback when I heard the news. My thoughts go out to his family and friends. My understanding is that it may have been a heart attack.
You will be missed Jim. RIP.
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
Jim was a great guy with a good sense of humor. He was very active in the Linux and Programming here in the Cincinnati area. I have known Jim for over 20 years and he will be missed by many. He was a very avid Ruby supporter and also of OpenSource. It is great to see him mentioned here on Slashdot, but a shame to hear the poor comments made about a man who cared about what he did. Free speech or not, it is nice to be respected.
Since when? Make is great. Even more so with GNU Make. It's portable, language agnostic, efficient, fast, scalable, parallelizable, easy to customize, text based, and so forth. This is why Make is still highly popular after 35 years. Yes, there are blogs that attempt to counter every one of those advantages but they also appear to be highly misinformed or biased, or they try to use make as a full all-in-one build system.
Yes, there are bad makefiles out there, but you can not prevent people using tools that they have not learned well, this is probably the biggest fault. But a fault that exists elsewhere (ie, the person trying to massively customize scons without knowing Python). I actually think that many of the problems people have when using make on bigger systems will actually happen with any automated system, the problem isn't with the tool itself but rather the lack of experience with how to manage a build of a large system, not planning ahead for the complexities that will always come, ending up with a system that was built up incrementally over years.
I'm not saying Make is perfect but I have not found alternatives that aren't bundled with their own larger set of warts. Rake is not bad (better than many of the alternatives I think), but you have to learn Ruby and its regexps to get stuff done, and it's documentation does not seem as comprehensive and clearly defined as I would like.