_why's work was much of what got me into Ruby in the first place. Not so much quirky as proudly both hyperliterate and unhinged, like the computing world's extension of depressed indie bands meeting David Foster Wallace in the early aughts.<p>Most of us that would've been into _why's stuff now have more traditional-looking jobs and responsibilities. But I'm so grateful for what he showed us then, and miss the more genuinely human, broken and vulnerable community he represented.
Hey folks. Not sure why this is here today, but happy to answer questions.<p>I've long held... complicated feelings about a lot of all of this. For an analysis I did of the work at the time, <a href="https://www.youtube.com/watch?v=MaWHVceDbFo">https://www.youtube.com/watch?v=MaWHVceDbFo</a>
Page 17 mentions a link and then goes off on a poignant meditation about its likelihood of breaking:<p><i>"It feels like I may have just gone ahead and ruined what I am by [dumping this link]. Has all of this writing lost its timelessness, to have this relic here? But maybe this link will never break, maybe it will stay there for all time. Maybe it's me. I'm a relic which is already out of his time in the present age."</i><p>The link is now broken. You weren't the relic, _why.
Would anyone be willing to explain this? Who is "us", what is a PCL, what is a spool, what are these random words? Is this supposed to be a puzzle?
_why offered a vision of computing, art and delight that we could maybe use more of nowadays. For more reference see “This Hack Was Not Properly Planned” here: <a href="https://web.archive.org/web/20080512050317/http:/hackety.org/2007/12/24/thisHackWasNotProperlyPlanned.html" rel="nofollow noreferrer">https://web.archive.org/web/20080512050317/http:/hackety.org...</a>
interesting timing, I've been thinking about _why lately; Brett Victor's recent update <a href="https://news.ycombinator.com/item?id=36596095">https://news.ycombinator.com/item?id=36596095</a> gave me _why vibes.<p>a thing I realized recently is that _why's disappearance ends up making his work more "Poignant" - the tech stuff washes away, but the story lives on. In that sense, it's a success.<p>if you look at old technology, the descriptions and documentation tend to outlast the artifacts. I like to imagine us as stage performers - any given implementation of a Shakespeare play only lasts a couple hours, but the structure of it is timeless. Perhaps we should all be writing more, implementing less.<p>also, it's always good to consider what fame is, and what it does to people. In an attention economy, we imagine that fame is wealth - but it's clearly not so straightforward
He and I went to high school together, and he was really funny then too.
In our seminary class, I would always ask him to play the Peanuts theme song on piano. I loved how he didn’t care what anybody thought and he just did his own thing.
I lost track of him after we graduated.
I'll take this opportunity to link to Why's Poignant Guide to Ruby - <a href="https://poignant.guide" rel="nofollow noreferrer">https://poignant.guide</a> - one of the most unique and inspiring programming language tutorials you'll ever read.
Worth reading through for a chuckle. Don't deprive yourself.<p>Why_ had a type of character we can easily forget used to exist, in this modern world where everyone is either slammed through cookie-cutters to become over-socialized slimy corporate people or medicated into a zombie-like state of partial existence.
GitHub is one of the most frustrating platforms to try to read a pdf on. Would anyone mind posting a direct link? It’s basically impossible to get it to show on my iPad, and I forget the raw url syntax at the moment.<p>Sorry for the unrelated comment, but maybe the direct pdf link will help others too.
My complicated feelings is that producing it and consuming it was all very unhealthy. There is nothing mystical about a machine and it isn't curious or interested that you can make a universal machine do the logic of any conceivable machine.<p>I feel these works did a lot to hobble people in their growth by putting too much emphasis on fantasy and not enough of actual understanding. I blame our mess of a JavaScript ecosystem on this idea that if you can dream it you can do it, and should do it, and that's wrong. It is like the old toddler wielding a knife thing, just because you found it doesn't mean you know what you have.