Friday, March 25, 2005

Just for Nish...

I know you are bored out of you gourd looking for stuff to go and check the blog roughly 237 times a day. So here's some stuff to keep you occupied, from all over the place and in no particular order:

New Star Wars trailer, actually makes Ep 3 look good? Discuss.

The boys from Penny Arcade played the guys at Bungie (creators of Halo) in Halo. Makes for some funny reading:
Pre-Game
Game results
Post-Game

What do you do if you are bored with a Civic and a Sawzall?

The coolest computer case ever built

We all know that All Your Base Are Belong To Us. But have you seen this? (requires sound)

And finally, the Industrial Revolution was neither industrial nor a revolution. Talk amongst yourselves.

The thing that just floored 'em.

Gooblar - The War Against Boredom

OK folks, here's the first finished track from the in-progress demo. It doesn't sound like I thought it would sound, but I think I like it. I ended up finding an amp to use (thanks, John!), but recording through the little dot microphone on my ibook doesn't leave a lot of sound options. I may re-record the vocals, but I'm not sure.

Comments, reactions, criticisms, tangents welcomed, nay, demanded.

Monday, March 21, 2005

Looking forward to thin-client? Not a chance.

This little essay is in response to the article here. It's required reading for this class, but I'm interested to see what other people's thoughts are about this.

Personally, I think this woman is crazy. Not because she is wrong, but because she is looking forward to it. There are very limited benefits to the end user, while the industry makes out like a bandit. Honestly, how often do you need remote access to your computer system? I rely on my computer much more than the average person, and even I don't need to access remotely often enough to set up a VPN. Which, by the way, is what companies already do if people need to dial in remotely. So why exactly does the average user need to be able to access his computer from any terminal in the world?

From the industry standpoint, on the other hand, the advantages never end. The name of the game in the software industry is control. The more control the company has over your use of the program, the more money they can extract out of you. Under the current system, you get a copy of the program on a cd, but you have to type a license number when install it, but then when you run the program you have authenticate it over the internet. You get incremental updates for free, but you have to pay again for any version updates. Under the new thin-client model, you don't even get a copy of the cd. What if you change your configuration and need to reinstall the program? You rely completely on the company to even verify that you bought the program in the first place.

Changing to a thin-client terminal also adds another layer of support that someone else has to provide. The way things are now, you are basically responsible for the upkeep and maintenance of your system. Under the new model, since the majority of the computing is done offsite somewhere else, you have to pay someone to maintain the system. Granted right now those of us that know computers end up helping the people that don't, but that's still better than paying someone else to do it.

Ms. Wood was right about bandwidth, that will definitely be a problem. She clearly doesn't know very much about server architecture, however, because she missed a problem that will make the bandwidth issues look like small potatoes. The infrastructure for a system that remotely provides all your computing applications would have to be unbelievably complex.

As an example, there exists a massive online role playing game called World of Warcraft. It is by far the most popular online game ever, with over 200,000 users. You can think of it as the game portion of an online operating system. There is no offline component, you must play it connected to the network. 200,000 users represents less than 1% of people that use computers on a daily basis, and obviously 1 game isn't as complex as an entire operating system running a host of programs. Even though, the servers crash on a regular basis, due to everything from database corruption (think online data storage) to general performance issues from slow hardware. This system represents the most sophisticated online network ever created, with hundreds of servers and millions in hardware, and it can barely keep up. The "Big 20" (the twenty oldest and most populated servers) have an uptime around 70%. How'd you like your computer to work only 70% of the time? And before you joke about how much your computer crashes already, keep in mind that represents an average uptime of 98%.

The last issue, which again Ms. Wood glazes over but misses for the most part, is cost. Blizzard charges $15 a month to access World of Warcraft, but they still can't afford to upgrade the hardware to the point they would like to. I should point out that $15 is after you shell out $50 for the initial purchase. Assume technology makes some advances and companies can afford to charge only $5 a month. You still have to pay a large monthly bill, even by conservative estimates. That's $5 each for the OS, a word processing program, a spreadsheet program, and a photo editing program. I'm assuming that web browsers and email applications will remain free, for the most part, but tack on another $5 if you use Outlook. At best, you're paying an additional $20 a month to access programs you've already had to pay for (remember the $50 for Warcraft?) and we haven't even talked about paying for online data storage yet.

Providing online email is one thing, but it's nowhere close to a thin-client OS. And I for one am happy about that, because when it does get here we'll all be paying more and getting less. And if you think I'm nuts, just click on the "Talkback" link in the article.

But I'm curious, what do "average users" think about thin-client computing?

Did he just say "steely knives"?

As it's clearly been way too long since I've posted anything, I won't even bother attempting to recap all that has transpired since my last real communiqué here (like Mark McGwire, I'm not here to talk about the past). Let's just say that skiing was totally awesome. Instead of coherence, I've opted for random anecdotage:

• Last night there was an 'open-mic night' at the bar in our dorm. As our friend Constantine organized it, I played a bit. It was ok, very very casual, but nice to be able to sing loud without fear of disturbing the neighbors. High point: a big African--sorry for the generic description, but I don't know what country he comes from; besides it reminds me of the guy from TV on the Radio's response when he was asked to account for the fact that there was a big African influence in their music: "that's probably because there's a big African in the band"--Anyway, a big African named 'Divine' played an acoustic, all-falsetto, totally unironic, and totally lovely version of the Backstreet Boys' "I Will Love You More Than That." It was sort of the best thing ever. He kinda sounded like Ben Harper, but, you know, good. You could tell he'd been singing it, very quietly, in his room every night, to learn the guitar. Low point: a sing-along of "that Eagles song," led by a very, very serious Albanian classical guitarist. Lesson learned: never trust anyone who knows all the lyrics to "Hotel California."

• Willy, did you know that genius (and perhaps cocaine) was so close to you?

• Questions raised by the Terri Schiavo case: 1) Can Congress just do this sort of thing whenever they want? Like if Bill Frist gets a parking ticket, can he summon an emergency session to quickly make legislation that says "Anyone named Bill Frist shall not be fined for parking illegally"? 2) How Kafkaesque is a government refusing to let one of its citizens die in order to protect 'the sanctity of life' (the sanctity, in this case, lying in the fact that without consciousness, she can't sin!)?

• I've started recording a demo in my very, very minimal spare time (I gets some more of that after the term ends wednesday. Woohoo!). Songs will be posted here as they get finished, in the next couple of weeks I hope.

Andy Rooney Time!

You want to know what I find annoying? Sure you do. "Inextricably linked" or "linked inextricably". It's one of the most annoying cliches I come across, and it bugs me just as much as other cliches. Like "Don't go there", "Don't get me started", or "too much information".

It's almost a reflex: when some people write "linked" they feel they must add "inextricably." Obviously, linked and inextricably linked mean different things. But it's become a parody of itself: linked is inextricably linked (in people's minds) to inextricably. And it's so overused now that the inextricable almost doesn't carry any meaning.

"And that's all I have to say about that."