Many “old iron” stories here. Back in the day, *real* computers blew up, shot out sparks and spewed smoke, and could be fixed with a good whack in the right spot. Not like today, when you can shut down entire cities from the comfort of your living room with a simple firmware security hole.
Meta-nostalgia is when you find one of your own nostalgiac postings in someone else’s nostalgia.
A fun little video of Simon Peyton Jones on useful -vs- useless languages, and trends in language design.
A little while ago, I finally got The Call.
“Hello?” I heard a gabble of voices on the other end, obviously a boiler room call.
“Sir? Mumble garble findows bhmflg wugga woop.”
“Excuse me? I can hardly hear you with all the noise on your end.”
“Sir? This is Miriam, calling from Microsoft Windows Support. How are you today?”
“I’m doing great! How are you?”
She hung up immediately.
It must have been something in my voice. I must have sounded too eager. I should have said something like, “I’m doing lousy, my computer isn’t working and I need expert to help me install spyware on my Windows PC,” or would that have been leading too much?
I don’t know why they even bother calling this area code.
Casey’s Blog is a great read (also, I’m really looking forward to The Witness).
He basically nails the state of the Windows input APIs (and a lot of other ones) here. I don’t want to publically skewer anyone, but let’s just say that marrying rent-seeking behavior (e.g., need for promotion by adding visible features) and territorialism (the need to protect your turf, especially when your stuff is poorly designed) don’t mix very well. Microsoft’s internal politics amplifies the bad. I’d love to see an official response to Casey’s issue.