Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

ConceptJunkie (24823)

ConceptJunkie
  (email not shown publicly)
http://conceptjunkie.blogspot.com/

Rick Gutleber

husband, father of 4, C++ and Tcl developer, Linux and Mac fan, aspiring composer;

interests: progressive music, MST3K, games, POV-Ray, food, photography

Journal of ConceptJunkie (24823)

Viruses

Monday August 25 2003, @11:22PM
User Journal
This whole "viruses/virii" argument is so stupid. First off, there are the Latin speakers who will argue 37 different reasons why such a word would or would not exist. Then there are the people who insist that virus is simply an English word and takes English pluralization.

Here's how it works. Hacker slang (or jargon, as in the "Jargon file") allows for the Latinesque construction of plurals by replacing "us" with "i", or "um" with "a" (or Anglo-Saxonish pluralization like "vaxen" or Hebrewish pluralization by adding "-im". Is this grammatically correct Latin (or Middle English, or Hebrew)? It doesn't matter... it's a play on words. The only point is that it is consistent with similar words.

What I find incredibly annoying is that people insist on using the "ii" suffix even though there is no precedent in real Latin, fake Latin or anything in between, presumably because it looks cool, or they have heard the word "radii".

Anyhow, that's my rant, and I'm sticking to it.

Microsoft Rules

Sunday March 16 2003, @11:12AM
Microsoft
I like Microsoft rule #3 so much I hate to change my sig to #4.

These are certainly not real rules, but are rules that Microsoft appears to follow by their actions.

Here are the others I've come up with:

Microsoft Rule #1: Every app must be expanded until it can be used as a vehicle for a virus that can trash the system. (In fact, no app is useful _unless_ it can be used as a virus vehicle. If MS wrote edlin today it would have scripting that could be used to access kernel functions via TCP/IP.)

Microsoft Rule #2: Flexibility in UI is acceptable, but defaults must confuse new users and frustrate experienced ones.

Microsoft Rule #3: GUI standards are no longer necessary. Shiny objects are always user-friendly.

Microsoft Rule #4: No useful thing can be designed unless by committee. Consistency and clarity are not signs of maturity. Simplicity is for amateurs. (Breaking up Microsoft would have about as much effect as asking a blind guy if he would not look over people's shoulders during the final exam.)

Microsoft Rule #5: Security has less "gee-whiz" factor than skinning and is therefore a less important feature. (Plus it's just too darn much trouble to check each memory buffer copy, especially when we'd rather spend time making the media player look like eyeballs.)

Microsoft Rule #6: Dominating a market is the same as excelling in a market ("Economic might makes right", or more simply "A monopoly means God smiles on everything you do.").

Microsoft Rule #7: Change is improvement by definition. (But this is universal among software companies...)