DIFY
Nobody cares. Do it for yourself.
-Hugh Macleod
For some yet unknown reason, Why the Lucky Stiff decided to delete his online presence. The previous link covers in detail all the information that is known about the situation and promises to keep up with any news found.
The first time I came across the name “_why” was while I was looking for blogs that focused on the Ruby Programming language back when I decied to learn Ruby. His blog Red Handed was recommended by many Rubyists. I found it odd and frustrating–_why rarely ever wrote in a linear fashion. Most of his posts were filled with what seemed like nonsense. Some people really dug his style and would leave nonsensical comments to his posts. It was almost like _why and his dedicated readers were speaking in a language you didn’t understand even though they were using English. I still found his content interesting enough to read all the posts in his blog archives. That’s when I found Hoodwink’d.
There were some odd hints of Hoodwink’d scattered across _why’s blog. You had to dig a little to figure out what it was. He purposefully made it difficult to “get in” by blocking admission through puzzles and weird hints. As I remember it, Hoodwink’d was comprised of a server piece hosted by _why, and a client piece written in Greasemonkey that you had to install in Firefox. Once the script was installed, you had to create an account on the server, and then you were granted access. When you would visit a web page, the Greasemonkey script would submit the page you were visiting to the server, fetch comments that other registered users had made about that page, then display them to you on the very same page. So say you would visit a blog post made by someone, you could see comments people were leaving about that post without the original author even knowing they were there. It was subversive, wicked, and creative all at the same time. I was blown away.
Some time after Hoodwink’d (I think), _why created Try Ruby. Try Ruby was a web page that had an interactive window that behaved like a command-line Ruby interpreter. You typed into it, the text was transmitted to a sandboxed Ruby interpreter, the interpreter would evaluate your input, then the results would be displayed back on the window. This in itself was pretty cool, but _why took it a step further: he made an accompanying interactive tutorial that taught you the basics of Ruby. Underneath the “interpreter” window was some explanatory text that would encourage you to type some input in. When you entered your text, not only would the interpreter display the evaluated results, but the tutorial window would change to the next lesson/topic. Words of encouragement and humorous comments were sprinkled in with the tutorial text. It was so well done and creative that I was again blown away.
After Try Ruby, _why wrote an article called “The Little Coder’s Predicament”. It lamented the fact that although programming power has increased over the years, we haven’t made programming easier for kids. He talked about how kids growing up around his time turned on a Commodore 64 and had a basic interpreter staring them in the face, daring them to make it do something. With your average Windows installation, there is little to help those who know nothing about programming yet want to create stuff. As an answer to this, he created Hackety Hack.
Hackety Hack was a downloadable Ruby environment that allowed you to create programs and share them with other Hackety Hack users. It had some of the same style as Try Ruby–interactive tutorials that walked you through creating gui applications that could talk to the web. One of the tutorials walked you through creating a chat application that, once created, would connect with other users and allow you to communicate with them. Again, it was so well done that my mind was blown.
_why had several other projects that he hosted. Some were completely creative like the above. Some were libraries used by enterprise-class users. He was even working on a new language he was designing called Potion.
Then a couple of days ago he just vanished. All his projects were taken offline without warning. All his sites are gone. All the mailing lists are gone. The code repositories are gone. The blogs with all their history are gone. His twitter account was deleted. People were shocked and a little worried.
Wherever he is, I hope he is okay and continues to create.
These links have been bouncing around the internet for a while, but they are so smile-worthy I wanted to post them to refer back to:
I want to make things that put me in the position of innocence, that recreate the feeling of innocence in you.
- Brian Eno