Actually, the phone that my wife had that died after about 6 months was a Nokia 3120. The only way to hang up on a call was to turn the thing off (and back on if you wanted to receive more calls) and the "6" key just didn't work. The one I had that I liked was the Nokia 8290 (finally found it).
Sorry, but I think this is a big deal. If I had known in 1990 that all my postings to Usenet would be publicly available many years after the fact, I might have thought twice before posting some of the articles I did, but now there are some postings from me around, that I am ashamed of 16 years later.
It's called "thinking about consequences" and it's not something that people tend to do, these days especially. You make "posts" on some "electronic forum". How did you think the posts would be there tomorrow for others to view other than through some persistent storage?
Plus, almost everyone, particularly young people, post all kinds of ideological, and frankly stupid, self-absorbed, etc., posts that come back to haunt them when they are more mature. I don't know of anyone who looks back at posts made 15 years ago and isn't a little embarassed by some of them and think, man... I was such an idiot back then. Funny thing is, you can't warn anyone (read: young people) about it either because they simply won't listen. We are all destined to make the same mistakes, mostly out of pride and ego.
I was needing a new cell phone before Christmas. I had a Nokia that had an internal antena, was thin, was small, was not a flip/clamshell form, and was built very well AND it fit perfectly into my front pocket comfortably. It had taken a lot of abuse over the few years I had it, from dropping it on the ground to accidentally sending it skipping across the pavement in a parking lot more than once.
Unfortunately, my wife needed a new phone because hers was broken. Well, to get her a new phone for reasonable cost, we had to upgrade our plan to a more 'modern' one and this forced me to upgrade my phone.
I couldn't find any phone that was similar to my old Nokia. All the phones now either have an external antena, are flip/clamshell, or both. I couldn't find any phone that was as small as the one I had from 3 years ago. None would fit into my front pocket comfortably, they were all too thick. External antenae are just out for pockets, they break too easily. To top it off, I couldn't find any phones without cameras that would come even close to my criteria. My job requires me to go into areas where cameras are not allowed. Also, I don't need Java, games, or any ring tones.
So, the era of a simple, practically indestructible, small, pocket-comfortable phone are over, it seems. Now it's all about cramming as much crap into the things as possible so the bullet-list can be long. Eventually, I had to settle on a phone that I'll have to leave at the security desk when I'm in those places but at least it doesn't have an external antena. It's still too thick to put into my pocket, though, so I have to wear it on my hip:(
There are numerous options other than the Microsoft VMs. I agree about it being nice to have a machine that can boot into all of the OSs though. However, in my experience, dual booting sucks because what we found is that the machine will stay in one OS 99.9% of the time and the other OS is just a waste of HDD space (as well as having to switch over to apply security updates and such). We went with having one OS per machine and just having more than one machine. It worked for us because we have multiple people needing to use machines as well. Other than that, a VM package (we use VMWare) can take care of the rest.
Actually, Sony is in a pretty hard place, right now, and probably fighting fires. Whether a brilliant marketing move by Microsoft of just pure luck on their part, Sony is in a bad position.
1) Blue Ray is a major issue. Not only is Sony having problems with BR itself, but once they committed, Microsoft was able to move on it. Now, with BR behind schedule, the release of the PS3 will cut (probably deeply) into the supply of drives for stand alone players. This will make it rough for the entire BR market. In any case, the delay of BR will mean expensive drives and media even without the internal competition within Sony for access to the drive supply.
2) Because of yields of Cell, Sony has had to back off on the system. They are cut back on the number of SPEs (7 now so that one bad one can be disabled and still have a viable chip) for the PS3 because of these yields which means that the minimum hardware will be lower than what was originally planned (8 SPEs originally). Not only that, but there is some speculation that Sony wanted to wait for a 45nm version for the PS3 that would have a lot more SPEs (like 16 or so) but due to market pressure, cannot wait another two years for it.
3) Microsoft Live was enough of a thread that Sony had to try to counter it. This takes resources (money and time).
4) The PS3 is now set for November of this year. 4a) Game makers for the PS3 will surely not be happy because of the long delay, meanwhile, XBox360 is *out* and able to gain traction. They can develop for the XBox360 *now* and make money. Staying with the PS3 is still spending money until the release. 4b) The XBox360 is, by all accounts, much easier to develop for and the PS3, by all accounts, offers only marginally more performance than the XBox360 - at the cost of lots more programming effort.
5) This delay and subsequent push of the deadline (speculation is that Sony wanted to actually release in 2007 but fear they cannot at the risk of losing the market too much) means that Sony is probably hemorhagging money right now on the PS3 only to come out with a compromised system that is expensive.
All that being said, there are lots of Sony PlayStation fans who will buy it no matter what, maybe even over the XBox360 (most of the console gamers I know currently have a PS2, an XBox, and an XBox360) so I expect it will still sell well. While I don't have an XBox360 yet (I do have PS2, XBox, and GC as well as some of the older ones), I have friends with them and I've played around with them. They are pretty nice and the XBox Live stuff is pretty darn neat.
Have you not seen any price lists in the last few days? The Conroe part as previewed is expected to be at/around $500USD. The FX-60 from AMD is over $1000USD, not that you can't get an Athlon64 X2 4800+ for just over $600USD, prices will surely drop by then but Conroe does look to be a bit faster.
One of the biggest arguments against DDR2-667 is that it performs roughly equal to DDR400 in real tests. If you take them with a grain of salt, the recent reviews of the AM2 Athlon64 actually ran slower on average with DDR2-667 than a comparable system (same clock rate and such) using DDR400 (although there were issues with that system being tested).
Bah, my math and numbers aren't right in the above but I still hold to the conclusions. There is supposed to be a speed bump of HT but I have the numbers wrong reflecting what the change is.
Oh... another thing that I forgot was that somewhere in the F, G, and H revisions (and probably the L), HT was supposed to be bumped up to 333MHz (1.333GHz effective) from the current 200MHz (1GHz effective). Given that tests have already shown that 800MHz effective HT performance is statistically equal to 1000MHz effective HT performance, boosting HT speed will probably give a small (1% to 3%) performance increase at best. In actuality, the HT speed increase is required for DDR2-800 to run at its best so the performance gain for it is probably inclusive to any gains shown by DDR2-800 adoption.
The things that AMD has said that they have are F, G, and H revisions of the K8 core (the core that the Athlon64, Turion, Sempron64s, and Opterons are based on) which, other than DDR2 support, not much more information is available. There is another revision called the K8L which will supposedly have 2x the FPU units for about a 50% gain in FPU performance. These will most likely be HPC blade Opterons or some such.
DDR2-800 support, which is the known upgrade, basically adds bandwidth to a chip that isn't bandwidth starved as it is. Current speculation is that the new DDR2-800 Athlon64s will show up to a 10% performance increase on extreme bandwidth benchmarks (synthetics and HPC crunchers, for example).
THe simple fact remains that intel needed to do these tests at all, side by side. That's an admission on their part that AMD is beating them and beating them hard.
Intel has publicly stated (admitted) this already. This demo is to show that the chips they have planned for Q3'06 release (speculation is that they will be delivering machines based on it in July which is the very beginning of Q3, which is only 4 months away) perform well.
By the way, if speculation is that machines will be selling in July, this would imply that the chips are in manufacturing even as we speak. This means that Apple is most likely to announce availability of the new Intel based Power Macs around this time, as well and the various benchmark sites to have their hands on 'pre-production' machines in two to three months tops. We'll be able to see the real story then.
The only announced things from AMD even remotely in this time frame (specifically July and Q3'06) are the AM2 socket for DDR2-800 and a speed bump of the FX-62 to 2.8GHz (which is the equivalent of the overclocked part in the demo). Given that DDR2-800 is expected to be a 10% speed bump at most in most cases and that Conroe will be available at 3GHz (if not higher as rumored - 3.33GHz), I predict (a rather easy prediction to make) that AMD will be playing catch-up for once in the past few years.
In my world, this just means I get another printer next time I'm at the store; probably a laser printer, and it also means that for color printing, I'll be booting windows.
Offtopic, but if you do get a laser, just get one that supports postscript and has a network interface. I have a Samsung CLP-550N and it works great with my Windows and my Linux boxes (just as a color postscript network printer using the standard networked printer port and stuff - cups deals with it great).
I'm doubtful of any energy surplus. From everything I've seen, producing biofuel costs more energy to make than is rendered by it. That means that it isn't sustainable, right now at least.
Actually, from what I understand, the zombie army owner already has "possession" of a zombie army. Say it numbers 100,000 machines. When you purchase the services, you purchase, say, 10,000 of his already zombie machines to send out your 1.2M emails.
According to the practices I've seen on TV, you "rent" or "purchase" time on the spammer's zombie army to send spam. So, spending $6500 to purchase the use of 10,000 zombies could be an interpretation of what was said. I don't know if this is what they meant and just didn't know what they were saying or what, though.
Yeah... there should be only one police force for the whole nation that has all the authority. Perhaps we should call it the Klandestine Government Bureau.
Sorry, you are as misguided as anything. 99.99% of the population has no desire to program, much less delve into kernel hacking. If it isn't there, these users will just find something that has it, not spend the next 5 years of their life figuring out how to program and then learning Linux internals (which will change before then) in order to write the support for their (now ancient) device. You lose.
Obviously, every kid wants to learn the internals of the OS that they are running. You are right that kids want to absorb knowledge, but you are wrong in assuming that they want to absorb *any* knowledge. If that were the case, why do kids to bad at some subjects and good in others (and this is on a per kid basis). Why do kids say "I don't like Subject$"? Shouldn't they just absorb it all?
It is typical geek narrowmindedness that assumes that every kid will want to learn something as esoteric and useless to 99.999% of the population as the internals of an OS, and this is spoken as a geek myself (who does know the internals of more than one OS).
There's also the issue in complexity as the Cell is not SMP. The PC (in the general sense) multi-core designs are SMP, which is a fairly simple and understood programming model (and we still can't get good auto-parallelizing compilers for it). The Cell isn't even remotely SMP in so many ways. First, the CPUs aren't the same. One is a basic PPC type but then you have all these others that are more like DSPs. The next thing is that the different CPUs have different access to memory. While the PPC has a 'normal' memory hierarchy (caches and such) and can access main memory 'trivially', the SPEs have static memory blocks and use DMA to push/pull data into that static memory. So the compiler has to not only deal with instruction streams, it has to deal with using that memory effectively... tiling, multi-banking, interleaving and such... which is typically algorithm based... so the compilers now have to figure out your algorithm, determine efficient memory allocation and windowing sizes, and so much more auto-magically, than a 'normal' compiler has to deal with. Not only that, but it also has to schedule in such a way for the SPE tasks to rendezvous with the PPC code in 'good' ways so as to not waste cycles on either the PPC or the SPE cores... and it has to do all that for every SPE... (X8). The Itanium compilers have a hard time finding parallelism in instruction streams and get heat because they aren't the best at that... now compare that to a compiler that has to figure out what parts of the instruction stream are useful to be translated to an SPE instead of the PPC (X8) and deal with all the DMA and memory blocking required for it to be efficient... basically figuring out your algorithm and making it better. And... it isn't useful to have one instruction ran on an SPE... you have to have reasonable streams to make the setup/teardown of the processes on the SPEs worthwhile.
I believe the best way to program such systems (for a while now and probably for a while to come) is to have libraries written to do specific things and programmers code against it. Perhaps some groups will make engines that run on a specified number of SPEs and those engines are used by a number of groups, similar to what we see in the game world today. Some company may make a physics engine that runs on, say, four SPEs and sell that to a number of groups, for example. Some other group may make a 3D sound engine that runs on one SPE. Another make a video engine that runs on two SPEs. A game company can take all three, glue them together and produce content and release a game. Even more cookie cutter games for us because the complexity of writing those engines will be high and different companies will be forced to use off-the-shelf engines because of time and money concerns.
The Cell is not new... TI has had similar architectures for years (typically ARM cores attached to a number of DSPs all on a single die). I've worked on similar systems. I wouldn't hold my breath waiting on this 'Octopiler' to be good.
Simple math based on market share show why malware writers haven't targeted much more than Windows (not that Windows isn't easily compromised). If you write something that has almost no chance or spreading around, or even if it does, won't do much, what's the point?
Now that Macs are getting popular, we'll see more of it... the same goes for Linux. It's simply a matter of time.
Yup... until the PS3 actually exists, it can do anything from play games to cure cancer to make a latte for me. It's easy to draw up a list of what you might do but it's a bit more to actually have it. Let me know when I can "have it".
Slashdot Mirror
Actually, the phone that my wife had that died after about 6 months was a Nokia 3120. The only way to hang up on a call was to turn the thing off (and back on if you wanted to receive more calls) and the "6" key just didn't work. The one I had that I liked was the Nokia 8290 (finally found it).
Sorry, but I think this is a big deal. If I had known in 1990 that all my postings to Usenet would be publicly available many years after the fact, I might have thought twice before posting some of the articles I did, but now there are some postings from me around, that I am ashamed of 16 years later.
It's called "thinking about consequences" and it's not something that people tend to do, these days especially. You make "posts" on some "electronic forum". How did you think the posts would be there tomorrow for others to view other than through some persistent storage?
Plus, almost everyone, particularly young people, post all kinds of ideological, and frankly stupid, self-absorbed, etc., posts that come back to haunt them when they are more mature. I don't know of anyone who looks back at posts made 15 years ago and isn't a little embarassed by some of them and think, man... I was such an idiot back then. Funny thing is, you can't warn anyone (read: young people) about it either because they simply won't listen. We are all destined to make the same mistakes, mostly out of pride and ego.
I was needing a new cell phone before Christmas. I had a Nokia that had an internal antena, was thin, was small, was not a flip/clamshell form, and was built very well AND it fit perfectly into my front pocket comfortably. It had taken a lot of abuse over the few years I had it, from dropping it on the ground to accidentally sending it skipping across the pavement in a parking lot more than once.
:(
Unfortunately, my wife needed a new phone because hers was broken. Well, to get her a new phone for reasonable cost, we had to upgrade our plan to a more 'modern' one and this forced me to upgrade my phone.
I couldn't find any phone that was similar to my old Nokia. All the phones now either have an external antena, are flip/clamshell, or both. I couldn't find any phone that was as small as the one I had from 3 years ago. None would fit into my front pocket comfortably, they were all too thick. External antenae are just out for pockets, they break too easily. To top it off, I couldn't find any phones without cameras that would come even close to my criteria. My job requires me to go into areas where cameras are not allowed. Also, I don't need Java, games, or any ring tones.
So, the era of a simple, practically indestructible, small, pocket-comfortable phone are over, it seems. Now it's all about cramming as much crap into the things as possible so the bullet-list can be long. Eventually, I had to settle on a phone that I'll have to leave at the security desk when I'm in those places but at least it doesn't have an external antena. It's still too thick to put into my pocket, though, so I have to wear it on my hip
There are numerous options other than the Microsoft VMs. I agree about it being nice to have a machine that can boot into all of the OSs though. However, in my experience, dual booting sucks because what we found is that the machine will stay in one OS 99.9% of the time and the other OS is just a waste of HDD space (as well as having to switch over to apply security updates and such). We went with having one OS per machine and just having more than one machine. It worked for us because we have multiple people needing to use machines as well. Other than that, a VM package (we use VMWare) can take care of the rest.
Actually, Sony is in a pretty hard place, right now, and probably fighting fires. Whether a brilliant marketing move by Microsoft of just pure luck on their part, Sony is in a bad position.
1) Blue Ray is a major issue. Not only is Sony having problems with BR itself, but once they committed, Microsoft was able to move on it. Now, with BR behind schedule, the release of the PS3 will cut (probably deeply) into the supply of drives for stand alone players. This will make it rough for the entire BR market. In any case, the delay of BR will mean expensive drives and media even without the internal competition within Sony for access to the drive supply.
2) Because of yields of Cell, Sony has had to back off on the system. They are cut back on the number of SPEs (7 now so that one bad one can be disabled and still have a viable chip) for the PS3 because of these yields which means that the minimum hardware will be lower than what was originally planned (8 SPEs originally). Not only that, but there is some speculation that Sony wanted to wait for a 45nm version for the PS3 that would have a lot more SPEs (like 16 or so) but due to market pressure, cannot wait another two years for it.
3) Microsoft Live was enough of a thread that Sony had to try to counter it. This takes resources (money and time).
4) The PS3 is now set for November of this year.
4a) Game makers for the PS3 will surely not be happy because of the long delay, meanwhile, XBox360 is *out* and able to gain traction. They can develop for the XBox360 *now* and make money. Staying with the PS3 is still spending money until the release.
4b) The XBox360 is, by all accounts, much easier to develop for and the PS3, by all accounts, offers only marginally more performance than the XBox360 - at the cost of lots more programming effort.
5) This delay and subsequent push of the deadline (speculation is that Sony wanted to actually release in 2007 but fear they cannot at the risk of losing the market too much) means that Sony is probably hemorhagging money right now on the PS3 only to come out with a compromised system that is expensive.
All that being said, there are lots of Sony PlayStation fans who will buy it no matter what, maybe even over the XBox360 (most of the console gamers I know currently have a PS2, an XBox, and an XBox360) so I expect it will still sell well. While I don't have an XBox360 yet (I do have PS2, XBox, and GC as well as some of the older ones), I have friends with them and I've played around with them. They are pretty nice and the XBox Live stuff is pretty darn neat.
Watch for it to be thrashed by the FX62 :).
Heh... the AMD machine was what the FX-62 is going to be...
And the Conroe EE part is expected to be a 3.33GHz part.
Have you not seen any price lists in the last few days? The Conroe part as previewed is expected to be at/around $500USD. The FX-60 from AMD is over $1000USD, not that you can't get an Athlon64 X2 4800+ for just over $600USD, prices will surely drop by then but Conroe does look to be a bit faster.
It's even worse than that. This isn't a brand new processor, it's a future processor that they hope to have out in 6 months.
Were you talking about Conroe or the upcoming FX-62? (both due at about the same time).
... and Godwin's Law is once again served.
:(
That aside, I'm with you DaveV1.0 but I have no mod points to give you
One of the biggest arguments against DDR2-667 is that it performs roughly equal to DDR400 in real tests. If you take them with a grain of salt, the recent reviews of the AM2 Athlon64 actually ran slower on average with DDR2-667 than a comparable system (same clock rate and such) using DDR400 (although there were issues with that system being tested).
Bah, my math and numbers aren't right in the above but I still hold to the conclusions. There is supposed to be a speed bump of HT but I have the numbers wrong reflecting what the change is.
Oh... another thing that I forgot was that somewhere in the F, G, and H revisions (and probably the L), HT was supposed to be bumped up to 333MHz (1.333GHz effective) from the current 200MHz (1GHz effective). Given that tests have already shown that 800MHz effective HT performance is statistically equal to 1000MHz effective HT performance, boosting HT speed will probably give a small (1% to 3%) performance increase at best. In actuality, the HT speed increase is required for DDR2-800 to run at its best so the performance gain for it is probably inclusive to any gains shown by DDR2-800 adoption.
The things that AMD has said that they have are F, G, and H revisions of the K8 core (the core that the Athlon64, Turion, Sempron64s, and Opterons are based on) which, other than DDR2 support, not much more information is available. There is another revision called the K8L which will supposedly have 2x the FPU units for about a 50% gain in FPU performance. These will most likely be HPC blade Opterons or some such.
DDR2-800 support, which is the known upgrade, basically adds bandwidth to a chip that isn't bandwidth starved as it is. Current speculation is that the new DDR2-800 Athlon64s will show up to a 10% performance increase on extreme bandwidth benchmarks (synthetics and HPC crunchers, for example).
THe simple fact remains that intel needed to do these tests at all, side by side. That's an admission on their part that AMD is beating them and beating them hard.
Intel has publicly stated (admitted) this already. This demo is to show that the chips they have planned for Q3'06 release (speculation is that they will be delivering machines based on it in July which is the very beginning of Q3, which is only 4 months away) perform well.
By the way, if speculation is that machines will be selling in July, this would imply that the chips are in manufacturing even as we speak. This means that Apple is most likely to announce availability of the new Intel based Power Macs around this time, as well and the various benchmark sites to have their hands on 'pre-production' machines in two to three months tops. We'll be able to see the real story then.
The only announced things from AMD even remotely in this time frame (specifically July and Q3'06) are the AM2 socket for DDR2-800 and a speed bump of the FX-62 to 2.8GHz (which is the equivalent of the overclocked part in the demo). Given that DDR2-800 is expected to be a 10% speed bump at most in most cases and that Conroe will be available at 3GHz (if not higher as rumored - 3.33GHz), I predict (a rather easy prediction to make) that AMD will be playing catch-up for once in the past few years.
In my world, this just means I get another printer next time I'm at the store; probably a laser printer, and it also means that for color printing, I'll be booting windows.
Offtopic, but if you do get a laser, just get one that supports postscript and has a network interface. I have a Samsung CLP-550N and it works great with my Windows and my Linux boxes (just as a color postscript network printer using the standard networked printer port and stuff - cups deals with it great).
I'm doubtful of any energy surplus. From everything I've seen, producing biofuel costs more energy to make than is rendered by it. That means that it isn't sustainable, right now at least.
Actually, from what I understand, the zombie army owner already has "possession" of a zombie army. Say it numbers 100,000 machines. When you purchase the services, you purchase, say, 10,000 of his already zombie machines to send out your 1.2M emails.
According to the practices I've seen on TV, you "rent" or "purchase" time on the spammer's zombie army to send spam. So, spending $6500 to purchase the use of 10,000 zombies could be an interpretation of what was said. I don't know if this is what they meant and just didn't know what they were saying or what, though.
Yeah... there should be only one police force for the whole nation that has all the authority. Perhaps we should call it the Klandestine Government Bureau.
Sorry, you are as misguided as anything. 99.99% of the population has no desire to program, much less delve into kernel hacking. If it isn't there, these users will just find something that has it, not spend the next 5 years of their life figuring out how to program and then learning Linux internals (which will change before then) in order to write the support for their (now ancient) device. You lose.
Obviously, every kid wants to learn the internals of the OS that they are running. You are right that kids want to absorb knowledge, but you are wrong in assuming that they want to absorb *any* knowledge. If that were the case, why do kids to bad at some subjects and good in others (and this is on a per kid basis). Why do kids say "I don't like Subject$"? Shouldn't they just absorb it all?
It is typical geek narrowmindedness that assumes that every kid will want to learn something as esoteric and useless to 99.999% of the population as the internals of an OS, and this is spoken as a geek myself (who does know the internals of more than one OS).
As another posted already... and Apache has has other worms in the past.
There's also the issue in complexity as the Cell is not SMP. The PC (in the general sense) multi-core designs are SMP, which is a fairly simple and understood programming model (and we still can't get good auto-parallelizing compilers for it). The Cell isn't even remotely SMP in so many ways. First, the CPUs aren't the same. One is a basic PPC type but then you have all these others that are more like DSPs. The next thing is that the different CPUs have different access to memory. While the PPC has a 'normal' memory hierarchy (caches and such) and can access main memory 'trivially', the SPEs have static memory blocks and use DMA to push/pull data into that static memory. So the compiler has to not only deal with instruction streams, it has to deal with using that memory effectively... tiling, multi-banking, interleaving and such... which is typically algorithm based... so the compilers now have to figure out your algorithm, determine efficient memory allocation and windowing sizes, and so much more auto-magically, than a 'normal' compiler has to deal with. Not only that, but it also has to schedule in such a way for the SPE tasks to rendezvous with the PPC code in 'good' ways so as to not waste cycles on either the PPC or the SPE cores... and it has to do all that for every SPE... (X8). The Itanium compilers have a hard time finding parallelism in instruction streams and get heat because they aren't the best at that... now compare that to a compiler that has to figure out what parts of the instruction stream are useful to be translated to an SPE instead of the PPC (X8) and deal with all the DMA and memory blocking required for it to be efficient... basically figuring out your algorithm and making it better. And... it isn't useful to have one instruction ran on an SPE... you have to have reasonable streams to make the setup/teardown of the processes on the SPEs worthwhile.
I believe the best way to program such systems (for a while now and probably for a while to come) is to have libraries written to do specific things and programmers code against it. Perhaps some groups will make engines that run on a specified number of SPEs and those engines are used by a number of groups, similar to what we see in the game world today. Some company may make a physics engine that runs on, say, four SPEs and sell that to a number of groups, for example. Some other group may make a 3D sound engine that runs on one SPE. Another make a video engine that runs on two SPEs. A game company can take all three, glue them together and produce content and release a game. Even more cookie cutter games for us because the complexity of writing those engines will be high and different companies will be forced to use off-the-shelf engines because of time and money concerns.
The Cell is not new... TI has had similar architectures for years (typically ARM cores attached to a number of DSPs all on a single die). I've worked on similar systems. I wouldn't hold my breath waiting on this 'Octopiler' to be good.
Simple math based on market share show why malware writers haven't targeted much more than Windows (not that Windows isn't easily compromised). If you write something that has almost no chance or spreading around, or even if it does, won't do much, what's the point?
Now that Macs are getting popular, we'll see more of it... the same goes for Linux. It's simply a matter of time.
Yup... until the PS3 actually exists, it can do anything from play games to cure cancer to make a latte for me. It's easy to draw up a list of what you might do but it's a bit more to actually have it. Let me know when I can "have it".