Why Emulate SCSI?

(From the trying-to-be-clever department)

A friend of mine was asking why so many interfaces are mapped to SCSI in the Linux world. Some people make some bogus argument that it acts as a handy abstraction layer that improves code reusability and reduces errors and blah blah blah.

Do not be fooled! This is just another example of software engineers overwhelming the public with heavy buzzwords in an attempt to distract them from the true goal, which is to prevent the obsolescence of one of the coolest acronyms the tech industry has ever produced. And make no mistake, cool acronyms are the primary product of the software engineering industry, and they always have been.

SCSI is one of the last great acronyms. It's kind of edgy, almost profane, and you can actually pronounce it. Just say it... "SCSI"... it just rolls off the tongue. Doesn't that feel good?

Now try sounding out "USB,", "IDE" or "IEEE 1394". They don't have the same ring to them, do they? And while we're at it, as Py once pointed out to me, why use the 9-syllable "WWW" in speech as an abreviation for the 3-syllable "World Wide Web"?

Acronyms are a dying art.

We need to hold onto SCSI for as long as we can. If I can't say "SCSI" at least once a week, I don't want to be a programmer any more! Luckily, I'm not alone. The kernel hackers are doing everything they can to keep it in use. True SCSI devices can die out for all we care. Even if it means we'll have SCSI sound, SCSI keyboards, SCSI mice, SCSI networking, and SCSI power switches, emulation will preserve SCSI forever!