20 July 2005

Jimmy Doohan: "It's Been Fun"

Filed under: — gxb @ 9:47 pm
tech icon movies icon tv icon

Last year I commented about what was described as (and in fact was) the last public apperance by Jimmy Doohan, known to countless Star Trek fans as Scotty, the ship's engineer. I wrote that entry as a eulogy for him, knowing (and hoping, for his sake) that it wouldn't be long before he died. He died today, after a (comparatively and mercifully) short struggle with Parkinson's, Alzheimer's, diabetes, and lung fibrosis (from his service in the Canadian military during WWII), at the age of 85.

I don't want to repeat everything I wrote before, but I'll say that Scotty was always my second-favorite character on the original Star Trek (after Spock), but Jimmy was probably my favorite member of the cast. I've never heard a bad thing said about him by anyone who ever met him, which included a lot of people. He didn't get along with Bill Shatner, but that's because of Shatner's ego. His fans included not only countless future engineers, but Neil Armstrong, the man who actually did go Where No Man Has Gone Before (exactly 36 years before Jimmy died). Unlike some actors who chafe at being typecast, or has-beens who cling to their past stardom like a life preserver, Jimmy grew to enjoy the fame that Trek brought him, and tried his best to give back to his fans. Next-Generation actor and self-described geek Wil Wheaton, commented that "Everyone who watched Star Trek liked Scotty, but everyone who met him loved Jimmy."

Once when asked about hearing the catch-phrase (which - for the record - was never actually spoken in an episode of the series) "Beam me up, Scotty," repeated over and over and over, he answered, "I'm not tired of it at all. Good gracious, it's been said to me for just about 31 years. It's been said to me at 70 miles an hour across four lanes on the freeway. I hear it from just about everybody. It's been fun."

Which pretty much sums it up.

May your dilithium crystals be fully charged, your matter/anti-matter reaction balanced, your wee bairns well cared for, and I wish you a safe and painless transport to your final shore leave.

Energise.

14 July 2005

Apple PCs

Filed under: — gxb @ 10:56 am
tech icon

If you follow technology news, there's a good chance you've heard that Apple has announced that they'll be switching to Intel processors in their Mac line, starting next year. This is fairly big development, and not just because of how it affects CPU manufacturers like Motorola, IBM (who makes Apple's current PowerPC CPUs), AMD, and (obviously) Intel.

One of the interesting implications of this is that, for the first time ever, Apple computers will be able to run Windows. Not through an add-in board like the Performa machine back in the 90's, and not through Virtual PC software which turns a fast Mac into a slow Windows machine. I mean simply running Windows. If you want, you'll be able to strip out Mac OS X and replace it with Windows XP.

At that point, "Macintosh" will cease to be a separate platform from the rest of the desktop-computing industry. Macs will be "PC compatible", and Apple will be just another brand of PC.

Of course the key difference is that only Apples will be able to run Mac OS X. Apple has promised to make it impossible to do this on anybody else's PCs (though it remains to be seen how successful they'll be at that). OS X is a really great operating system, so I don't expect much of anybody who buys an Apple will really erase OS X and replacing it with Windows. But some of them might still replace it with Linux. In fact, some already do; there's a version of Linux engineered specifically to run on Macs.

But whether or not OS X gets hacked to run on Dells or HPs, this will point out to consumers that: PC ≠ Windows. People (even technical people who should know better) refer to the "PC version" of a program such as Photoshop, when they really mean the "Windows version". That's an important distinction, because there are PCs out there that don't run Windows. More than a few of them, in fact. Most of them run Linux, a smaller number run FreeBSD or one of its cousins, a few run BeOS, and so on. I have a bunch of PCs on my network; only two of them run Windows-compatible application software.

I can see a lot of future Apple owners installing both Windows and OS X on their Intel-powered Macs, and selecting which OS to run depending on whether they want to surf the web safely or do video editing (OS X), or play games or run some specialised shareware app (Windows). Owners of Dell or HP PCs might respond by installing both Windows and... Linux (second cousin of OS X, with similar anti-spyware/virus advantages), or a revitalized BeOS (a great multimedia OS that Microsoft conspired to keep locked out of the market).

The bottom line may be that people stop thinking that buying a PC necessarily means using Windows. And that can only be good for the technology industry, by poking a hole in the Microsoft near-monopoly and perhaps even restoring competition to the software market.

7 June 2005

.XXX

Filed under: — gxb @ 11:31 am
sex icon tech icon law icon

The Powers That Be on the internet have decided - to my surprise - to approve the creation of a .XXX top-level domain. The arguments for it are so weak, and the arguments against it are - once you think about them - so compelling, that I figured that ICANN (the PTB in question) would continue saying "um no" to the proposals. Instead, they've said "yes", and are currently working out the fine print before it goes live.

There are some arguments for doing it, but they don't hold up to scrutiny. The standard argument for creating new top-level domains is overcrowding of .COM. "All the good names are taken," they say, and they're right. But when they opened .NET and .ORG to let anyone use them for any purpose, .COM didn't get any less crowded. When they created .BIZ and .INFO, .COM was still saturated. Because no one with a .COM domain is going to just give it up for a new one in a less well-known namespace. When .XXX registration opens, you can be sure that every porn purveyor with a .COM domain will rush to register the corresponding .XXX domain. And keep them both. It'll just be a land rush to grab real estate in the New World... with no improvement in the Old World.

Another argument for creating .XXX is that it'd be easy for parents, schools, and businesses to just block the whole domain from the computers used by their children, students, and employees. They certainly have every right to do that. But that won't do a damn thing to block the petabytes of porn already in the .COM domain. So it'll be ineffectual. The horse has fled the barn; there's no point in fixing the door now.

Unless, of course, it were possible to move all that porn from .COM to .XXX. But it's not. ICM Registry - the people who'll be handling registration of this domain - stress the fact that the use of .XXX will be voluntary. And short of the UN imposing legislative authority over its members (as if that could happen without nuclear missles flying), there's no way to require all porn sites to relocate. If someone in Ukraine registers PORNBBQ.COM and puts photos of people fucking on a web server, there's nothing the Attorney General of the U.S. can do about it (short of nukes like those I just mentioned).

I just wish I could be so sure that the A.G. wouldn't try. So far, the U.S. government has been comparatively restrained (mostly by the courts, not self-restraint) in trying to legislate content restrictions on the internet. There's been that whole "free expression" thing getting in the way. But what if there were a segment of the internet specially made for sexually-explicit material? Gee, forcing Americans to "label" that material with a .XXX domain wouldn't deprive them of their free expression rights, would it?

That's the argument they'll make, but it's a bit like those "free speech zones" the government creates to keep protestors out of the way. It takes speech off the corner of Main Street and Common Avenue, and shoves it into an alley in a part of town most people avoid. This web site contains sexually-explicit material, which means it'd probably be carted off to the .XXX ghetto. But it also contains material that has every moral (and Constitutional) right to be heard. Putting it in .XXX would mean it'd be blocked from lots of colleges, libraries, and even ISPs catering to the non-porn-buying market. The bottom line: the ideas of people like me get less distribution. The keepers of the public morals would love that.

I've read the fine print of what's been announced, and find some of the details troubling. For one thing, ICM Registry proudly states that they have no prior connection to the porn industry. So... why are they getting involved in it? One obvious answer is money. They see a lot of people making a lot of money from this internet porn stuff, and they want a piece of the action. And quite a piece it'll be, with $60/year for each domain registered. All for running a web site with a medium-sized database behind it. And of course ICANN itself gets a cut of that, which is no doubt the "argument" that finally swayed them to approve it.

Another bit from the fine print is that the organisation that will be setting policy for .XXX has an agenda. They're honest about it, and it's not as bad as "take over the world", but they're definitely not neutral administrators, like the original domain registrars were. They policy setting agency is called the International Foundation For Online Responsibility, and their agenda includes: setting business-practise standards for anyone who runs a .XXX site, promoting the free-expression parts of the UN Declaration of Human Rights, maintaining the privacy of porn customers, protecting children online, and wiping out child pornography. Like I said: not malevolent. I support a lot of it. But it's an agenda nonetheless, and that's bad for anybody who happens not to share it.

And it means that if you register a .XXX domain, they claim a right to tell you how to run your business. You have to take the steps they deem appropriate for keeping children from accessing your site. And regardless of your views on child pornography (and reasonable people can disagree over whether CGI images or imaginary fiction are "OK"), you have to agree to abide by their standards. For example, you can't have a domain name intended to entice pedophiles into visiting your site. But what if you're trying to wean the kid fanciers from their vice, by offering them barely-legal teenagers? Isn't that a legitimate choice someone ought to be allowed to make? Not under IFFOR's rules. It's not even clear whether someone who wants to run a site that isn't pornographic is allowed to use .XXX.

Their policies might arguably make for a better .XXX domain. But there are the unintended consequences to consider as well: They'll push the most irresponsible site operators and the sites most likely to exploit children out of .XXX and back to... (where else?) .COM. Um, isn't that the place we wanted to remove them from?

I can see this as a kind of circle-the-wagons, Comics-Code-Authority way for the mainstream, business-oriented porn industry to set up a club for those who want to play by their rules, setting everyone else up to be devoured by wolves. Got kicked out of .XXX for using an unapproved method of restricting access to minors? Too bad. Wrote an article calling for the decriminalization of virtual kiddie porn or advocating that the age of consent be lowered? Get out. Someone falsely accused you of doing something IFFOR considers ethical, but convinced them it was true? Tough. There's even the potential for the management of IFFOR to become something of a mafia/cartel, controlling who's allowed to sell porn from the safety of .XXX and who isn't. It's bad enough when the government steps in and regulates an industry that strongly; it'd be even worse for an agency that's accountable to no one but their board of directors.

3 May 2005

Son of God's ex-Boyfriend

Filed under: — gxb @ 10:42 pm
me icon tech icon

It's been a month since God half-smote my web server, rendering the original site un-update-able, at least not without a lot of manual hacking. But "God's ex-Boyfriend" is back now, better than ever. Or something.

I've overlaid a live WordPress-based site on top of the now-fully-static Movable-Type-based site. I'm going to link them together as best as I can, but ultimately they'll be two distinct sets of articles. I'm using one of WordPress' default appearance templates for now, but I'll fix that soon, taking advantage of this opportunity to freshen the look of the blog, which is a kind of Son of God's ex-Boyfriend.

Be careful how you parse and interpret that, though. It's not (Son of God)'s ex-Boyfriend. (That'd be James, the "disciple Jesus loved" but who got left behind when He ascended into heaven). It's not Son of (God's ex-Boyfriend), referring to me, the person. (I'm quite certain that I have no offspring out there.) It's Son of "God's ex-Boyfriend", referring to the blog.

I don't plan any radical changes in the nature of the blog, though. Just a return to what I was doing before. So thanks for coming back (or visiting for the first time, if that's the case).

1 May 2005

Volume One

Filed under: — gxb @ 12:00 am
tech icon

For earlier articles on this topic, see God's ex-Boyfriend, volume one.

Powered by WordPress