Kapelson

When I was 12 or 13 (around the same time as above), I was told I was getting something "very special" for Christmas. I thought it was a drumset, and I was PSYCHED. Turns out it was a Sony CLIÉ.

Still though, it was pretty nice. I still remember trying to figure out how to develop games for it. My household didn't have the internet at the time and my access to the library was limited (we lived on a farm), so in the end I was just a 13 year old who had a machine with all of his classmates' names and birthdays organized on it.

What a time to be alive.

Maybe it's a momentum thing: an arrow with more wood would be heavier, and as a result it would create a greater impact.

Weird metaphor indeed.

Ugh, don't remind me. Now THAT's a student-pessimistic system if I ever saw one.

The idea here though is that mobile devices will eventually become versatile enough to be used in these environments. My phone has an HDMI output and bluetooth capability, what, other than current usage patterns, is keeping Android/iOS from allowing you to plug in a monitor and hook up a keyboard to a phone? Hell, they are already doing it (albeit poorly): http://www.motorola.com/Consumers/US-EN/Consumer-Product-and...

The point is, I already carry around a phone in my pocket, and eventually, when I get into the office, I will hook it into my monitors/keyboard/mouse, and work away. The PC cannot keep up, and will eventually be replaced by this paradigm.

I treat obfuscated code as a kind of puzzle. "Given a crazy string of seemingly random semicolons and numbers, can you discover what it does and how it works?" It's like a magic eye puzzle for a programmer.

Regardless of whether he was being a dick or not, the issue is still there. A helpful dick is still valuable, and banning him is really only hurting the project as a whole.