![]() |
A Very Workman-Like Pagefor an ENGL366E assingment,lovingly thrown together by Mike Sugimoto |
Without further ado, let's get started.
ccTLD | Where is it? | Want one? | Obnoxiously overused by.. |
.tv | Tuvalu | nic.tv will sell you one for $1,000 USD | .. TV marketing executives and producers. Saving grace: Has not exploded into mass-media meme. Yet. |
.am | Amernia | $200 from amnic.net | .. nobody, yet. I
just can't figure out who'd want one. Run for your life: Won't stay this way for very long. |
.to | Tonga | get it from tonic.to for about $50/year | .. easily amused Web designers who think URLs like
"surf.to" and "come.to" are spiffy. Saving grace: Strong anti-spam policy |
.cc | Cocos Islands | $100/2 years from nic.cc | .. an awful lot of
people, for reasons I can't understand. Saving grace: None of my friends fall into this category. |
.tm | Turkministan | too bad | .. people concerned about
trademarking. Saving grace: You can't get one anymore. |
.fm | Federated States of Micronesia | $200
initially, then $100/year afterwards from dot.fm. | .. FM radio
stations; 100.3 the Q. Saving grace: "It's a premium domain name!" |
In my world, the most important file compression methods are gzip and bzip2. gzip is a freely-available derivative of the old Unix compress, which didn't work all that well and had all kinds of irritating quirks that used to drive people like me nuts (until we all changed to gzip, anyway). Technically speaking, it reduces the size of files using Lempel-Ziv coding (LZ77), and plain-text files (source code, HTML documents, that kind of stuff) can expect compression ratios of up to 60-70%, which isn't bad.
Although it isn't a standard or anything, it is pretty much the universally accepted way to distribute files in the Unix world -- purists will argue that you should only use compress to do this, since it's the only compression utility available by default in all flavors of Unix, but these people probably still think vi is a good editor as well and should probably be ignored.
To compress a file using gzip, the syntax looks like this:
bzip2 is a relative newcomer to the compression game, but it is quickly becoming a favorite of administrators all over the network. It compresses better than gzip and comes with its own libraries so geeks like me can write applications that take advantage of it -- but that's really secondary to the fact that it compresses files really well. I used to make Linux kernels using gzip to compress the imgaes; using bzip2 instead lets me get down to 3/4 the size of the gzip'd equivalent. Syntax is functionally identical to gzip, and this is fast becoming a popular way to send big files around between Unix systems.
Most people, however, don't use gzip, or bzip2 to pack multiple files together. Instead, we use tar, the tape archiver, which bundles files into one convenient package (but does not compress any of them). To assemble a "tarball" (collection of files compressed and packed up for shipping), you say something like this:
There's another option that's become popular with some people recently, at least for the distribution of applications -- the package bundle. RedHat made the format popular with their RPM (RedHat Package Manager) format, but most commercial Unices (Solaris, HP-UX, IRIX) have been using some kind of package system for quite some time. Still, I think package managers are for weenies -- real men use tarballs.
Although it isn't specified in any of the above-referenced documents, avoidance of several tags -- BLINK, BGSOUND, EMBED, and FRAME -- is mandatory if you don't want an angry mob of users to come burn your server farm to the ground.
External resources: Assembled by high school students, Bloody Painful: Crime and Punishment in Elizabethan England was a fascinating read, particularly if you've read other works like John H. Langbein's Torture and Plea Bargaining. The high school kids in Springfield, IL, have done an amazing job on a number of Elizabethan topics.
Other classes: Despite their excellent classics archive and on-line edition of the plays, MIT's Course 21L (Literature) is kind of disappointing as far as courses on The Bard go. 21L.009 is the major Shakespeare course for the Institute, and depending on section you may or may not spend most of your time in a dark room watching films of the plays. (Or so promises Peter Donaldson, 21L.009's F00 instructor.) Diana Henderson's entry for this semester seems more interesting: "Why is Shakespeare `the central author of the English-speaking world'?"
Speaking of which, the old standby of American literary theory -- the Partisan Review -- is now on-line. Sadly, only miniscule portions of their content is available on the Web; the availability of articles, past and present, is a big selling point of Philosophy and Literature, "exploring the dialogue between Literary and theoretical studies and philosophy."
What would be useful: There's an interesting theory that there are really only eight or nine different kinds of stories in literature, and so there's really nothing new. What I want is a system like Xrefer's, except that encompasses the totality of "great" literature; I want to be able to backtrack across Shakespeare's plays and see how they relate back to Homer, and then move forward in time and see the other works that Homer influenced.. basically, I want a hypertext cross-referenced library -- so we can play "six degrees of historical thought."
Nope, I'm not asking for much.