In my case, it was Microsoft that told me to ditch IE. At least I think that was the message they were trying to send when windows update introduced a buggy version that kept me from using IE to read my webmail or check my credit card ballance online. I'm much happier now that I'm using Safari on OS X.
House of Pancakes vs. House of Carpets (their products sound AND taste the same)
If munching carpet really tasted like a short stack of buttermilk pancakes with maple syrup, I wouldn't be gay. Well not as gay at any rate.
Yours in Christ,
shoeboy
The beautiful thing about Scrabble
on
Word Up
·
· Score: 1, Troll
Is how it can help us become better Christians. The ability to spot patterns in seemingly random collections of letters is also key to understanding the hidden messages in the bible.
It's all about the acrostics, man. I'm actually working on a unix program to parse the KJV and reassemble the spiritual truths contained in the first letter of each verse. Look for it on freshmeat.
Now I don't mean to imply that my penis is larger than yours or that my opinons are more valid. Only that I've had my account longer than you've had yours. This makes me better than you.
But has anyone considered that maybe other companies don't consider Microsoft's technology to be worth licensing? I don't even think it's worth pirating, myself.
I cannot count the amount of times an NT server had to be manually power cycled because a service hung and wouldn't restart. This wasn't some oddball, third party service; this was IIS ("WWW Publishing Service" I believe)
I cannot count the amount of times I've heard NT blamed by ignorant users. On the resource kit, and also on the 2000 Server install CD is a pair of tools called tlist and kill. I thought every NT admin knew about those?
Do you reboot Linux when a userland process hangs too?
Ok, I think we can all agree that M$ has been making life hard on Linux advocates. First off they come out with Windows 2000 which doesn't crash and then they follow it up with Windows XP which also doesn't crash.
Of course, this hasn't stopped us from complaining about Windows stability (a true zealot is never deterred by facts), but it has made us look a bit ridiculous.
So what happens when Windows becomes secure (assuming this happens). It'll be a sad day for Linux advocates everywhere is what will happen. Window will then join VMS, OSX and FreeBSD in being basically superiour to Linux. Thank god for BeOS going extinct, because, as a Linux advocate I jsut don't think I could bear that.
Anyway, Micro$haft (he he, aren't I original), please don't make a secure product. Please, I'm begging you.
Shocked to find advertising going on here. The next thing you know I'll be getting unsolicited commercial snail mail from local retailers. This must be stopped!
From now on I'm only buying from companies that don't advertise or give away freebies. Novell is probably the best bet. They've shown a complete inability to market Netware for years now.
Just because Amazon turns a slight profit doesn't make your stocks worth anything.
In addition to raising money through sale of stock, Amazon has also raised money by selling bonds. Lots of bonds. The ammount of securities debt Amazon is carrying is far more than the total value of the company.
Now for the fun bit: when push comes to shove, bondholders get paid before stockholders. Always. The people who loaned the company will get paid back before the people who bought part of it. Now it's worth noting that the securities amazon.com has issued are trading at very low rates. They're junk bonds. The market thinks there's a good chance that Amazon will not be able to cover the interest payments on those bonds in the long term. If that happens, the shareholders get $0.00 from any sale of assets.
This makes Amazon.com a risky buy. Not as bad as VA Software, (people find Amazon's services useful afterall) but still risky.
He's not talking about the Mozilla project, he's talking about the transition from 3.0 to 4.0. Basically Netscape threw away a lot of good code and some very nice algorithms for the sake of newness. They also developed a java fixation while the language and libraries were still very immature.
By the time the Mozilla project was announced, Netscape was already out of marketshare and had a product that was cleary inferior to ie 4. Considering the amount of bugs in the initial release of ie 4, making an inferior product was no easy feat.
Jamie Zawinski has a great deal to say about this period in Netscapes history.
I am more than capable of making an on topic post here, but I shan't. Instead I'd like to take a moment to talk about my cock, if I may, to familiarize you with the events that are about to take place. It resembles nothing in shape so much as a fire extinguisher; a red cylinder with a circumference about equal to a petri dish and as long as a regulation yardstick, networked with throbbing veins big enough to drive a Matchbox car through, and topped by a nearly luminescent magnificent red head, as big as a mid-size cantaloupe and covered in skin the consistency of #4 grain sandpaper. I could fit your little sister's arm in my urethra.
So I'll come over to your house, introduce yourself to your Mom and talk a little bit about what I'm going to do to your anus, lay down some tarps on the floor, and commence what will no doubt be the crowning achievement of your life, even better than censoring slashdot. I will sodomize you like God was riding on my shoulder whispering instructions into my ear, Mr. Sims, and this is how it'll be done.
When i was dating a girl who rather enjoyed being fisted, the first thing I learned was how to 'make the ducky,' or shape your hand into a position that could slip into the vagina with the least resistance. Then, when entrance had been achieved, the position of the hand was changed to a fist to offer more stimulus. Unfortunately, my teenage ass-toy, my cock cannot make the ducky. It's just going to have to use brute pelvic force to stretch your brown-walled turd canal to it's utmost. You may wish to practice in the intervening hours with King Cobra malt beverage bottles, just to reduce the intense, searing pain a notch or two.
There will be pain, however, and I am not cruel. I will provide you with a damp rag to clutch between your teeth, muffling the grunts and lamentations from your mouth. One would think that my pleasure would be reduced from this measure, but I must confess that I find the sounds of your rupturing colon and the gases escaping sufficiently erotic to continue my explorations. Once my cock has reached it's limit, buried deep inside you like Grant in Grant's Tomb, the true sex will begin. You and I will bond like few men can, and I may finally come to know your affection for censorship, whcih I have never supported and never will, and you will begin to know the blinding joy of forced male sodomy.
And, as few people know (well, actually, Vladinator knows, as my pimp, and spiralx of course, and John Katz from that time in the bunker when we both thought we were going to die, and Elby and Jelerial of course know in exchange for the free hosting, and CmdrTaco, Hemos, Jamie, Timothy and Pudge know as valued johns, and as Rusty knows because he's from the Kur0shin.org and I fucked him), my penis is covered in a number of barbs, much like a dog's, and during coitus, these prevent my unit from slipping out of the blood-lubricated hole and disrupting my tearing rhythm. Upon orgasm, as pints of spooge rocket out of my pee-hole, burning through whatever they encounter like that burny stuff in the Alien movies, the barms withdraw and my flaccid member can resume it's rightful place in my pants.
Unfortunately, Michael Sims, once I had worked my monster cock all the way up your digestive system, your immense, man-tittied disgustingness would make it impossible for me to ever have an orgasm again, and my penis would be stuck running parallel to your spinal column for the forseeable future. Of course, I'd cut your arms and legs off to lighten the load a bit, and have my Dad bring over the Makita power sander so I wouldn't have to look at your foolish face with the first little wisps of a moustache growing (and I've heard hair grows after you die, so I bet that thing'll look REALLY BITCHIN once you're super dessicated) and I'd just have to wait for you to rot yourself off of my dick, as I'll be damned if we're gonna do any cutting in there. Needless to say, this does not appeal to me.
Sadly, however, I see no other options. Best tell your mom I'm on my way. I'd like peanut butter sandwiches and a tall, cool glass of milk to be waiting for me. It's gonna be a long day.
Hate is a great uniter. Hate makes you strong. Every movement must have someone to hate.
If Microsoft played by the rules, what then? If you think KDE vs. Gnome is bad now, just wait until they aren't competing against Microsoft anymore.
I don't support Microsoft's tactics, but I really don't want to see KDE extremisist parading Miguel de Icaza's severed head around on a pike with a banner reading "The Konquered Kompetitor." I really don't want to see UC Berkely burned to the ground by BSD hating Linux zealots.
So what's needed is an enemy that's wholly evil, but doesn't have a crushing competetive advantage (that's krushing kompetitive advantage for you KDE users).
My suggestion: Break up Microsoft and create a small, federally funded software development house called evilsoft. Evilsoft will have a mandate to create unpleasant software and market it in unwholsome ways, but it will be limited to 50 employees. This will give Sun, Oracle, Apple and the OSS community a common foe while also allowing fair competition.
I know/. readers are suspicious of government involvement, but I really see this as the only option. Unfortunately, the answer to "can't we all just get along?" is "only if we all hate the same thing."
I urge you to write your congressperson today, if you aren't a US citizen, pick a congressperson at random and claim to be overseas military personell.
It's nice to get 4 coffee breaks a day when the server's down, but I tend to think people would actually rather WORK.
If you have experience with NT/2000 servers crashing 4 times a day, I would heavily recommend that you either replace your faulty hardware or fire your administrator. Once a month I can understand (although 3 months of uptime is usual for an NT or 2000 server) but you exaggerate far too much. Furthermore, in a PC environment you can still work even when the server is down unless you're using a web or database application (or Citrix). If you're using a web or db app, there's nothing to stop you from using unix as the db or web server (in fact, I'd recommend it), but there's nothing wrong with NT or 2000 as a file server. Furthermore, you can run 2000 as your windows client, reduce client crashes to once a month or so and even deal with a lot of those by rebooting weekely (few workplaces have a lot of users at 3am Sunday morning, that's a good time.)
I'm afraid the stability arguement just doesn't hold up and hasn't really applied since the release of NT 4 workstation.
If they want to do something fancy, like find a file, they can't do it.
Start->FSearch->For files or folders (Windows 2000)
Defaults to searching all local hard drives and is quite simple. If you don't like the gui, there's always "Dir/S" for filename searches and "FindStr/S" for content searching. I fail to see how find and grep or an X windows file manager are any easier to use. A bit more powerful in certain cases I'll grant, but how often does the average user need to use a recursive grep? Enough to justify the time required to learn how to do it? I doubt this somewhat although I'm willing to accept proof to the contrary.
Windows is easy to learn and hard to use, while *nix is hard to learn but easy to use.
I keep hearing this, but I haven't heard any supporting arguements. Can you point me to comparitive time trials for Un*x vs. Windows at performing common tasks? By common tasks I mean directory traversal, document creation and editing, searching and the like.
Usability is a topic that interests me a great deal, so I'd love to see some hard figures here.
The author misses the simple fact that ie and MS Office don't run on Linux. This means that Linux users have to settle for "mostly good enough" document exchanges and a "mostly good enough" web experience. Like it or not, the OSS office solutions aren't fully interoperable with Microsoft's proprietary document formats. This can be immensely frustrating to the user. When you consider the growing unwillingness of major websites to support Netscape and simple fact that ie is more forgiving of poorly written html, you get very unhappy users.
So it comes down to a matter of priorities: do you want users who are satisfied with their experience but difficult to support or users who feel that their environment is unusable and who hate your guts.
My question is "if you aren't satisfying the users with your solution, why provide one at all?"
We should all keep in mind this simple truth: Code Red is dying.
You don't need to be Kreskin to predict Code Red's future. The hand writing is on the wall: Code Red faces a bleak future. In fact there won't be any future at all for Code Red because Code Red is dying. Things are looking very bad for Code Red. As many of us are already aware, Code Red continues to lose market share. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
Famed Code Red using hacker mafiaboy states that there are 7000 machines that are victims of Code Red. How many users of Nimda are there? Let's see. The number of Code Red versus Nimda posts on Usenet is roughly in ratio of 1 to 4. Therefore there are about 7000*5 = 35000 Nimda users. Code Red on Linux posts on Usenet are about half of the volume of Code Red on Windows posts. Therefore there are about 700 victims of Code Red on Linux. A recent article put Code Red on *BSD at about.008 percent of the virus infection market. Therefore there are (7000/100)*.008 =.56 Code Red on FreeBSD machines. This is the result of one guy working in his spare time to port Code Red and consistent with the number of Code Red on FreeBSD Usenet posts.
Due to the troubles of Sircam, abysmal infection rates and so on, Sircam is getting out of the virus business and becomming a flight simulator. Code Red is still dying and the corpse of Code Red will soon be turned over to another charnel house.
All major surveys show that Code Red has steadily declined in market share. Code Red is very sick and its long term survival prospects are very dim. If Code Red is to survive at all it will be among virus hobbyists, dabblers, and dilettantes. Code Red continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Code Red is dead.
If they'd only used FreeBSD instead of Lunix. FreeBSD has a less restrictive license, superior design, a more stable userland API and better performance.
I don't understand this sick obsession with Lunix, can someone explain it to me?
--Shoeboy
If you don't want to take out a 2nd mortgage to add a screamingly loud, 35 lb. heat sink/fan combo to your box, you can go with a superior processor design that doesn't produce as much heat.
Professional audio on Lunix? You've got to be kidding me. I'm fluent in English, which is something of a rarity on this site, and I interpret Professional Audio as "audio suitable for professionals."
News flash: professionals can afford to pay for software. They don't need half assed hobbyis crapware because they can afford professional software.
Lets be honest, Lunix is the same price as *BSD, has a more restrictive license than *BSD, isn't as well designed as *BSD and has a much less mature development model.
Could someone please tell me why the worst open source OS gets the most publicity?
Slashdot Mirror
Yours in Christ,
shoeboy
If munching carpet really tasted like a short stack of buttermilk pancakes with maple syrup, I wouldn't be gay. Well not as gay at any rate.
Yours in Christ,
shoeboy
Is how it can help us become better Christians. The ability to spot patterns in seemingly random collections of letters is also key to understanding the hidden messages in the bible.
It's all about the acrostics, man. I'm actually working on a unix program to parse the KJV and reassemble the spiritual truths contained in the first letter of each verse. Look for it on freshmeat.
Yours in Christ,
--Shoeboy
Now I don't mean to imply that my penis is larger than yours or that my opinons are more valid. Only that I've had my account longer than you've had yours. This makes me better than you.
That is all.
--Shoeboy
Anyone who says "the internet has changed everything" should be shot.
Lessig lost all credibility when the bubble burst. The internet has changed nothing and theft is still theft.
--Shoeboy
--Shoeboy
But has anyone considered that maybe other companies don't consider Microsoft's technology to be worth licensing? I don't even think it's worth pirating, myself.
--Shoeboy
Windows isn't easy to install. That's why it comes preinstalled on new computers.
--Shoeboy
I cannot count the amount of times I've heard NT blamed by ignorant users. On the resource kit, and also on the 2000 Server install CD is a pair of tools called tlist and kill. I thought every NT admin knew about those?
Do you reboot Linux when a userland process hangs too?
Yours,
--Shoeboy
Ok, I think we can all agree that M$ has been making life hard on Linux advocates. First off they come out with Windows 2000 which doesn't crash and then they follow it up with Windows XP which also doesn't crash.
Of course, this hasn't stopped us from complaining about Windows stability (a true zealot is never deterred by facts), but it has made us look a bit ridiculous.
So what happens when Windows becomes secure (assuming this happens). It'll be a sad day for Linux advocates everywhere is what will happen. Window will then join VMS, OSX and FreeBSD in being basically superiour to Linux. Thank god for BeOS going extinct, because, as a Linux advocate I jsut don't think I could bear that.
Anyway, Micro$haft (he he, aren't I original), please don't make a secure product. Please, I'm begging you.
Your former employee,
--Shoeboy
Shocked to find advertising going on here. The next thing you know I'll be getting unsolicited commercial snail mail from local retailers. This must be stopped!
From now on I'm only buying from companies that don't advertise or give away freebies. Novell is probably the best bet. They've shown a complete inability to market Netware for years now.
--Shoeboy
Just because Amazon turns a slight profit doesn't make your stocks worth anything.
In addition to raising money through sale of stock, Amazon has also raised money by selling bonds. Lots of bonds. The ammount of securities debt Amazon is carrying is far more than the total value of the company.
Now for the fun bit: when push comes to shove, bondholders get paid before stockholders. Always. The people who loaned the company will get paid back before the people who bought part of it. Now it's worth noting that the securities amazon.com has issued are trading at very low rates. They're junk bonds. The market thinks there's a good chance that Amazon will not be able to cover the interest payments on those bonds in the long term. If that happens, the shareholders get $0.00 from any sale of assets.
This makes Amazon.com a risky buy. Not as bad as VA Software, (people find Amazon's services useful afterall) but still risky.
--Shoeboy
The irony, the irony.
He's not talking about the Mozilla project, he's talking about the transition from 3.0 to 4.0. Basically Netscape threw away a lot of good code and some very nice algorithms for the sake of newness. They also developed a java fixation while the language and libraries were still very immature.
By the time the Mozilla project was announced, Netscape was already out of marketshare and had a product that was cleary inferior to ie 4. Considering the amount of bugs in the initial release of ie 4, making an inferior product was no easy feat.
Jamie Zawinski has a great deal to say about this period in Netscapes history.
--Shoeboy
I am more than capable of making an on topic post here, but I shan't. Instead I'd like to take a moment to talk about my cock, if I may, to familiarize you with the events that are about to take place. It resembles nothing in shape so much as a fire extinguisher; a red cylinder with a circumference about equal to a petri dish and as long as a regulation yardstick, networked with throbbing veins big enough to drive a Matchbox car through, and topped by a nearly luminescent magnificent red head, as big as a mid-size cantaloupe and covered in skin the consistency of #4 grain sandpaper. I could fit your little sister's arm in my urethra.
So I'll come over to your house, introduce yourself to your Mom and talk a little bit about what I'm going to do to your anus, lay down some tarps on the floor, and commence what will no doubt be the crowning achievement of your life, even better than censoring slashdot. I will sodomize you like God was riding on my shoulder whispering instructions into my ear, Mr. Sims, and this is how it'll be done.
When i was dating a girl who rather enjoyed being fisted, the first thing I learned was how to 'make the ducky,' or shape your hand into a position that could slip into the vagina with the least resistance. Then, when entrance had been achieved, the position of the hand was changed to a fist to offer more stimulus. Unfortunately, my teenage ass-toy, my cock cannot make the ducky. It's just going to have to use brute pelvic force to stretch your brown-walled turd canal to it's utmost. You may wish to practice in the intervening hours with King Cobra malt beverage bottles, just to reduce the intense, searing pain a notch or two.
There will be pain, however, and I am not cruel. I will provide you with a damp rag to clutch between your teeth, muffling the grunts and lamentations from your mouth. One would think that my pleasure would be reduced from this measure, but I must confess that I find the sounds of your rupturing colon and the gases escaping sufficiently erotic to continue my explorations. Once my cock has reached it's limit, buried deep inside you like Grant in Grant's Tomb, the true sex will begin. You and I will bond like few men can, and I may finally come to know your affection for censorship, whcih I have never supported and never will, and you will begin to know the blinding joy of forced male sodomy.
And, as few people know (well, actually, Vladinator knows, as my pimp, and spiralx of course, and John Katz from that time in the bunker when we both thought we were going to die, and Elby and Jelerial of course know in exchange for the free hosting, and CmdrTaco, Hemos, Jamie, Timothy and Pudge know as valued johns, and as Rusty knows because he's from the Kur0shin.org and I fucked him), my penis is covered in a number of barbs, much like a dog's, and during coitus, these prevent my unit from slipping out of the blood-lubricated hole and disrupting my tearing rhythm. Upon orgasm, as pints of spooge rocket out of my pee-hole, burning through whatever they encounter like that burny stuff in the Alien movies, the barms withdraw and my flaccid member can resume it's rightful place in my pants.
Unfortunately, Michael Sims, once I had worked my monster cock all the way up your digestive system, your immense, man-tittied disgustingness would make it impossible for me to ever have an orgasm again, and my penis would be stuck running parallel to your spinal column for the forseeable future. Of course, I'd cut your arms and legs off to lighten the load a bit, and have my Dad bring over the Makita power sander so I wouldn't have to look at your foolish face with the first little wisps of a moustache growing (and I've heard hair grows after you die, so I bet that thing'll look REALLY BITCHIN once you're super dessicated) and I'd just have to wait for you to rot yourself off of my dick, as I'll be damned if we're gonna do any cutting in there. Needless to say, this does not appeal to me.
Sadly, however, I see no other options. Best tell your mom I'm on my way. I'd like peanut butter sandwiches and a tall, cool glass of milk to be waiting for me. It's gonna be a long day.
Your daddy,
--Shoeboy
Hate is a great uniter. Hate makes you strong. Every movement must have someone to hate.
/. readers are suspicious of government involvement, but I really see this as the only option. Unfortunately, the answer to "can't we all just get along?" is "only if we all hate the same thing."
If Microsoft played by the rules, what then? If you think KDE vs. Gnome is bad now, just wait until they aren't competing against Microsoft anymore.
I don't support Microsoft's tactics, but I really don't want to see KDE extremisist parading Miguel de Icaza's severed head around on a pike with a banner reading "The Konquered Kompetitor." I really don't want to see UC Berkely burned to the ground by BSD hating Linux zealots.
So what's needed is an enemy that's wholly evil, but doesn't have a crushing competetive advantage (that's krushing kompetitive advantage for you KDE users).
My suggestion: Break up Microsoft and create a small, federally funded software development house called evilsoft. Evilsoft will have a mandate to create unpleasant software and market it in unwholsome ways, but it will be limited to 50 employees. This will give Sun, Oracle, Apple and the OSS community a common foe while also allowing fair competition.
I know
I urge you to write your congressperson today, if you aren't a US citizen, pick a congressperson at random and claim to be overseas military personell.
It's our last, best hope.
--Shoeboy
So you've got a computer with a clear plexiglas case.
That ain't nothin. I'm wearing clear plastic trousers. People keep congratulating me on my " miniature components."
--Shoeboy
It's nice to get 4 coffee breaks a day when the server's down, but I tend to think people would actually rather WORK.
If you have experience with NT/2000 servers crashing 4 times a day, I would heavily recommend that you either replace your faulty hardware or fire your administrator. Once a month I can understand (although 3 months of uptime is usual for an NT or 2000 server) but you exaggerate far too much. Furthermore, in a PC environment you can still work even when the server is down unless you're using a web or database application (or Citrix). If you're using a web or db app, there's nothing to stop you from using unix as the db or web server (in fact, I'd recommend it), but there's nothing wrong with NT or 2000 as a file server. Furthermore, you can run 2000 as your windows client, reduce client crashes to once a month or so and even deal with a lot of those by rebooting weekely (few workplaces have a lot of users at 3am Sunday morning, that's a good time.)
I'm afraid the stability arguement just doesn't hold up and hasn't really applied since the release of NT 4 workstation.
--Shoeboy
If they want to do something fancy, like find a file, they can't do it.
/S" for filename searches and "FindStr /S" for content searching. I fail to see how find and grep or an X windows file manager are any easier to use. A bit more powerful in certain cases I'll grant, but how often does the average user need to use a recursive grep? Enough to justify the time required to learn how to do it? I doubt this somewhat although I'm willing to accept proof to the contrary.
Start->FSearch->For files or folders (Windows 2000)
Defaults to searching all local hard drives and is quite simple. If you don't like the gui, there's always "Dir
--Shoeboy
Windows is easy to learn and hard to use, while *nix is hard to learn but easy to use.
I keep hearing this, but I haven't heard any supporting arguements. Can you point me to comparitive time trials for Un*x vs. Windows at performing common tasks? By common tasks I mean directory traversal, document creation and editing, searching and the like.
Usability is a topic that interests me a great deal, so I'd love to see some hard figures here.
Thanks,
--Shoeboy
Well there's just one problem here: applications.
The author misses the simple fact that ie and MS Office don't run on Linux. This means that Linux users have to settle for "mostly good enough" document exchanges and a "mostly good enough" web experience. Like it or not, the OSS office solutions aren't fully interoperable with Microsoft's proprietary document formats. This can be immensely frustrating to the user. When you consider the growing unwillingness of major websites to support Netscape and simple fact that ie is more forgiving of poorly written html, you get very unhappy users.
So it comes down to a matter of priorities: do you want users who are satisfied with their experience but difficult to support or users who feel that their environment is unusable and who hate your guts.
My question is "if you aren't satisfying the users with your solution, why provide one at all?"
Any answers?
--Shoeboy
We should all keep in mind this simple truth: Code Red is dying.
.008 percent of the virus infection market. Therefore there are (7000/100)*.008 = .56 Code Red on FreeBSD machines. This is the result of one guy working in his spare time to port Code Red and consistent with the number of Code Red on FreeBSD Usenet posts.
You don't need to be Kreskin to predict Code Red's future. The hand writing is on the wall: Code Red faces a bleak future. In fact there won't be any future at all for Code Red because Code Red is dying. Things are looking very bad for Code Red. As many of us are already aware, Code Red continues to lose market share. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
Famed Code Red using hacker mafiaboy states that there are 7000 machines that are victims of Code Red. How many users of Nimda are there? Let's see. The number of Code Red versus Nimda posts on Usenet is roughly in ratio of 1 to 4. Therefore there are about 7000*5 = 35000 Nimda users. Code Red on Linux posts on Usenet are about half of the volume of Code Red on Windows posts. Therefore there are about 700 victims of Code Red on Linux. A recent article put Code Red on *BSD at about
Due to the troubles of Sircam, abysmal infection rates and so on, Sircam is getting out of the virus business and becomming a flight simulator. Code Red is still dying and the corpse of Code Red will soon be turned over to another charnel house.
All major surveys show that Code Red has steadily declined in market share. Code Red is very sick and its long term survival prospects are very dim. If Code Red is to survive at all it will be among virus hobbyists, dabblers, and dilettantes. Code Red continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Code Red is dead.
--Shoeboy
If they'd only used FreeBSD instead of Lunix. FreeBSD has a less restrictive license, superior design, a more stable userland API and better performance.
I don't understand this sick obsession with Lunix, can someone explain it to me?
--Shoeboy
If you don't want to take out a 2nd mortgage to add a screamingly loud, 35 lb. heat sink/fan combo to your box, you can go with a superior processor design that doesn't produce as much heat.
Need a hint? Try this.
--Shoeboy
Professional audio on Lunix? You've got to be kidding me. I'm fluent in English, which is something of a rarity on this site, and I interpret Professional Audio as "audio suitable for professionals."
News flash: professionals can afford to pay for software. They don't need half assed hobbyis crapware because they can afford professional software.
Lets be honest, Lunix is the same price as *BSD, has a more restrictive license than *BSD, isn't as well designed as *BSD and has a much less mature development model.
Could someone please tell me why the worst open source OS gets the most publicity?
Your friend,
--Shoeboy