Where the hell is mp3board injured by the mere existence of Gnutella?
The injury could come from the Gnutella search box on the mp3board front page. MP3board feels it's being sued because it gives access to the Gnutella net. Kind of like Ford being sued because it uses Firestone tires. Yes? No? Maybe?
No company that had nearly $120 million in the bank to burn is small. But that's just a small quibble. More importantly, why is being small a justification for patent protection? Are you saying (for example) that drug companies who invest billions of dollars and years of time in R&D shouldn't have the right to patent their drugs and protect their investement for a few years just because they are big (and bad)?
First off, what profits? Making buckets of cash? Not any time soon. Anyway, the investors want Transmeta public so they can sell their shares (probably bought for $1 a piece, maybe less) at market prices ($10, $50, $100, who knows). The investors don't share profits (even if there were any). Understand now?
I think Williamette is named after a river in Oregon close to Beaverton.
Actually its Willamette, which rhymes with dammit, and it runs through Portland, OR. The river is near Beaverton in the way that Queens, NY is near the Empire State Building.
If you're curious as to why Intel codenames are named after Pacific Northwest (Deschuttes, Coppermine, etc.) rivers, it's probably because Intel's suburban Portland sites are the largest in the company and do a significant amount design and production there.
"No one should ever need more than 640k of RAM." - Bill Gates.
What you said is just about as short-sighted as what BillG said way back when. YOU may not need 1.5GHz today, but some other people do today and many more will need it in the future.
AFAIK, Willamettes will be available in Q3 2000.
PS: There ARE lots of high-bandwidth x86 boxes out there.
Well a company like Amazon could probably be very accurate about how much business they lost. A ton of money flows into Amazon every day. In the Oct, Nov, and Dec 1999, they took in about $676 million. So 2 hours of downtime could cost them 676m/90 days/24 hours * 2 hours = $626,000, over $5,000 a minute.
So by your logic, I should get some cans and string and run them between me and the 911 dispatch office in case someone were to DoS attack the 911 system? Or how bout this case, should I not feel sorry for you if you're being taken to a hospital in an ambulance, but some idiot on the road won't get out of the ambulance's way and you happen to die before you reach certain lifesaving at the hospital? The road hog denied you an important service. I'm certainly not saying E-trade is as important as 911. But my point is that someone asked "how does this affect me"? E-trade provides a valuable service to a lot of people, most of whom are not fat cats and/or day traders, and denying them access to that service can really hurt them. There is probably is some web service that you (or your job) depends on somehow and if it were DoS'd at a critical time you be pissed too. And you wouldn't want some jackass to say "well you shoulda planned for that".
I was talking just yesterday with a person who was familiar with MS's public Internet connections and architecture. It is highly distributed, with huge data centers all around the world, with sophisticated load balancing and failover. From what he said, it seems like an effective DoS attack on the high-traffic portions of MS's web presence would be very difficult. Then again, I ASSUME that Yahoo is highly distributed and well load-balanced and they were taken down all the same.
You're haven't been listening, have you? The rivers are CODENAMES. Pentium is a PRODUCT name. Kind of like your nickname is IDIOT, but you're real name is JOE. Get it?
Oh yeah, Deschuttes is a river in Oregon (and the name of a damn fine brewery). Another one is Klamath in Oregon. And always remember Denial is a river in Egypt.
Merced and Willamette are codenames, not product names. They're taken (like many predecessors) from rivers in and around Oregon where Intel does a lot of design and fabrication. Merced is in California. Willamette (thymes with dammit) is in Oregon. Coppermine is in Canada. Can't remember any others off the top of my head.
I am well aware that Moore's Law is not a rule and that Intel chip designers still have to show for work on Monday. I used it in the context of whether this is a Big Deal(tm) or not. A 4GHz CPU would be awfully nice to have in 2000, but Moore's Law predicts that in 2003 or 2004 4GHz might just be run of the mill. Just trying to inject a little perspective, that's all.
IBM says 1 GHz will be available in a year, but Intel will definitely ship 1 GHz Willamette CPU's in under 12 months. So in the near term, this isn't a Big Deal. IBM also says that the 3.3 to 4.5 GHz chips are 3 to 4 years out. Intel is currently shipping 800MHz chips. So by Moore's law, they should have 3.2 GHz in about 36 months. If IBM had a 3.3 GHz CPU shipping in exactly 36 months (3 years), Intel would only be 3% slower. So maybe this isn't such a Big Thing?
Then you've obviously never worked on a software project before. It's impossible to fix and find all the bugs in a product. Doesn't matter where to code came from, it can't be done. So your choices are to never release it because it still has bugs or decide which bugs you can tolerate still being in the code when you relase. Presumably once you release, you start pounding on the remaining bugs for a point fix. Whether there are bugs in the retail Win2k that should've been fixed before release remains to be seen, but in the meantime MS has done exactly what every other software team in history has had to do: bite the bullet, kick it out the door and hope it works in the real world. PS: Only Knuth code is bug free.
I'm not suprised SP2 is already in the works. The SPs aren't just bug fixes. New functionality is often included, a la NT 4 SP3 adding DirectX for the first time. So the SPs probably partially contain features cut from the 1.0 release. And, I'm sure Win2k had a looong list of bugs postponed for the release. SP1 and SP2 are probably just prioritized (hopefully by severity) from the 1.0 bug list. It's just smart dev management.
FYI: Beta follows alpha, so a future milestone could be declared a beta version, not the reverse. Also note that the mozilla milestone chart lists (roughly) monthly milestones, so that M19 at the bottom should not be construed as a potential release or even beta version.
Slashdot Mirror
Where the hell is mp3board injured by the mere existence of Gnutella?
The injury could come from the Gnutella search box on the mp3board front page. MP3board feels it's being sued because it gives access to the Gnutella net. Kind of like Ford being sued because it uses Firestone tires. Yes? No? Maybe?
Any guesses on exactly which "major software company" Brian Kirkby worked for or what product X is/was?
My uneducated guesses are Novell and GroupWise.
No company that had nearly $120 million in the bank to burn is small. But that's just a small quibble. More importantly, why is being small a justification for patent protection? Are you saying (for example) that drug companies who invest billions of dollars and years of time in R&D shouldn't have the right to patent their drugs and protect their investement for a few years just because they are big (and bad)?
First off, what profits? Making buckets of cash? Not any time soon. Anyway, the investors want Transmeta public so they can sell their shares (probably bought for $1 a piece, maybe less) at market prices ($10, $50, $100, who knows). The investors don't share profits (even if there were any). Understand now?
I think Williamette is named after a river in Oregon close to Beaverton.
Actually its Willamette, which rhymes with dammit, and it runs through Portland, OR. The river is near Beaverton in the way that Queens, NY is near the Empire State Building.
If you're curious as to why Intel codenames are named after Pacific Northwest (Deschuttes, Coppermine, etc.) rivers, it's probably because Intel's suburban Portland sites are the largest in the company and do a significant amount design and production there.
Now why was this on-topic reply moderated down?
... is a Beowulf cluster of these things.
Then why does the header say "News for Nerds" instead of "Discussion Forums about Linux Kernel Point Releases for Nerds"? Maybe it's a typo.
I guess what you meant by "real" was "a benchmark where Windows lost" and "any OS not made by Microsoft".
Just wait 'til Transmeta hits 1GHz: orgasmic posts of glee for Linux and gloom and doom for Intel, no matter how fast their latest CPU runs.
"No one should ever need more than 640k of RAM." - Bill Gates.
What you said is just about as short-sighted as what BillG said way back when. YOU may not need 1.5GHz today, but some other people do today and many more will need it in the future.
AFAIK, Willamettes will be available in Q3 2000.
PS: There ARE lots of high-bandwidth x86 boxes out there.
procedings take place on Quake 3 Arena server?
Well a company like Amazon could probably be very accurate about how much business they lost. A ton of money flows into Amazon every day. In the Oct, Nov, and Dec 1999, they took in about $676 million. So 2 hours of downtime could cost them 676m/90 days/24 hours * 2 hours = $626,000, over $5,000 a minute.
So by your logic, I should get some cans and string and run them between me and the 911 dispatch office in case someone were to DoS attack the 911 system? Or how bout this case, should I not feel sorry for you if you're being taken to a hospital in an ambulance, but some idiot on the road won't get out of the ambulance's way and you happen to die before you reach certain lifesaving at the hospital? The road hog denied you an important service. I'm certainly not saying E-trade is as important as 911. But my point is that someone asked "how does this affect me"? E-trade provides a valuable service to a lot of people, most of whom are not fat cats and/or day traders, and denying them access to that service can really hurt them. There is probably is some web service that you (or your job) depends on somehow and if it were DoS'd at a critical time you be pissed too. And you wouldn't want some jackass to say "well you shoulda planned for that".
I was talking just yesterday with a person who was familiar with MS's public Internet connections and architecture. It is highly distributed, with huge data centers all around the world, with sophisticated load balancing and failover. From what he said, it seems like an effective DoS attack on the high-traffic portions of MS's web presence would be very difficult. Then again, I ASSUME that Yahoo is highly distributed and well load-balanced and they were taken down all the same.
But I have perfectly functioning DSL, so I sold my modem and can't dial up anymore. What would I do then?
You're haven't been listening, have you? The rivers are CODENAMES. Pentium is a PRODUCT name. Kind of like your nickname is IDIOT, but you're real name is JOE. Get it?
Oh yeah, Deschuttes is a river in Oregon (and the name of a damn fine brewery). Another one is Klamath in Oregon. And always remember Denial is a river in Egypt.
Merced and Willamette are codenames, not product names. They're taken (like many predecessors) from rivers in and around Oregon where Intel does a lot of design and fabrication. Merced is in California. Willamette (thymes with dammit) is in Oregon. Coppermine is in Canada. Can't remember any others off the top of my head.
I am well aware that Moore's Law is not a rule and that Intel chip designers still have to show for work on Monday. I used it in the context of whether this is a Big Deal(tm) or not. A 4GHz CPU would be awfully nice to have in 2000, but Moore's Law predicts that in 2003 or 2004 4GHz might just be run of the mill. Just trying to inject a little perspective, that's all.
I did use 18 months, not 12.
800 * 2 = 1600 in 18 months, then 1600 * 2 = 3200 in another 18 months. 18 + 18 = 36 = 3 years.
IBM says 1 GHz will be available in a year, but Intel will definitely ship 1 GHz Willamette CPU's in under 12 months. So in the near term, this isn't a Big Deal. IBM also says that the 3.3 to 4.5 GHz chips are 3 to 4 years out. Intel is currently shipping 800MHz chips. So by Moore's law, they should have 3.2 GHz in about 36 months. If IBM had a 3.3 GHz CPU shipping in exactly 36 months (3 years), Intel would only be 3% slower. So maybe this isn't such a Big Thing?
Then you've obviously never worked on a software project before. It's impossible to fix and find all the bugs in a product. Doesn't matter where to code came from, it can't be done. So your choices are to never release it because it still has bugs or decide which bugs you can tolerate still being in the code when you relase. Presumably once you release, you start pounding on the remaining bugs for a point fix. Whether there are bugs in the retail Win2k that should've been fixed before release remains to be seen, but in the meantime MS has done exactly what every other software team in history has had to do: bite the bullet, kick it out the door and hope it works in the real world. PS: Only Knuth code is bug free.
I'm not suprised SP2 is already in the works. The SPs aren't just bug fixes. New functionality is often included, a la NT 4 SP3 adding DirectX for the first time. So the SPs probably partially contain features cut from the 1.0 release. And, I'm sure Win2k had a looong list of bugs postponed for the release. SP1 and SP2 are probably just prioritized (hopefully by severity) from the 1.0 bug list. It's just smart dev management.
FYI: Beta follows alpha, so a future milestone could be declared a beta version, not the reverse. Also note that the mozilla milestone chart lists (roughly) monthly milestones, so that M19 at the bottom should not be construed as a potential release or even beta version.