Hit by the flaw, Bitten by the patch. Lyrics by me.
I got hit by the flaw, and bitten by the patch A computer rebuild, a 'driver with a ratchet It's hit me, it'll be hitting you How much did you pay for that Sony Doo-Doo?
I Put a music CD in my CD-Drive Hit "I Accept" to some DRM jive Now I'm here, waiting for the other shoe and to make it worse, the music sucked too
Hit by the flaw, bitten by the patch That company just said bend-over biatch Bitten by the patch, hit by the flaw hold on to your hat, 'cause that ain't all
Picked it up this morning from the TV news Sony got another system that you don't want to use As if the first one was'nt bad enough, with your computer flubed up They got a second system that's also bad enough
Hit by the flaw, bitten by the patch some big CEO needs to take it up the ass
"That's enough now, I'm Tired" - Oppourtunites never knock - The Clash - version where the kid sings it.
Who state (paraphrased) "Our customers don't know how badly we have fucked up their computers, so why should they care that we fucked up their computers so badly that any half compitant thief can steal their personal data, savings, and life?"
Way to go guys.
I used to think that I stopped buying music when I turned 25, because I stopped having disposable income. Turned out that the music just sucked, and the asses putting it out kept trying to give me diseases.
Yesterday, when the author of the study was interviewed - I attempted to read the PDF. I could not get it with Mozilla 1.5rc3 and Acrobat reader7. From the authors comments, I had some questions about the methodology.
The Blog Commentary makes several good points about applying "The Windows Way", and configuration management. From the commentary, I can glean that the packages to run on the SUSE box were, shall we say - sub-optimal. Additionally, it appears that the Server was installed with the Kitchen Sink.
While installing the computer with the Kitchen-Sink (TM) options is a bad idea on any Server - it is often done on Windows, and rarely done on Linux. Thus, the patch list summary produced (Windows Patches Linux Patches) would seem questionable on it's face. (No, I can't spell Priema Facia.)
If the systems at download.microsoft.com could have stood up to the slashdotting yesterday, the comment probably would have been modded a 5 here. Since many of us could not get the study to read, it is nice to have it linked.
* A recent regression that either crashes or breaks certain usages of innerHTML for dynamic applications. (315189/315999)
* A recent regression and most common RC2 crash (316025)
Hopefully, this will resolve most of my issues.
Remember, if you can't wait a day or so for the auto update: Help -> Check for Updates. (If you are running a RC of 1.5)
I have an old iRiver H-120. (It's about three years old). My wife hates the interface,butIlove the unit.
1) Connects to CLIENT Win2K; XP boxes via USB as a external HD WITHOUT any drivers 2) FM radio 3) 20GB storage 4) Battery,so I don't have to worry about getting power to "a self powered external case" when I use laptops, or older machines 5) Internal Microphone & recording capability, for when I need to verify details / have a cranky and difficult customer. 6) Marginally larger than an old iPod
The requirement here sounds like it was to be X pages with Y formatting. You can change the formatting on OOo. The formatting should have met the specs.
Open Source is largely sucessful when there is a large enough community of quality contributers. They have seen a problem, and are trying to solve it. A company, on the other hand is management directed. The dichotomy of this problem is that an Open Source Company must have "Management" trying to direct what is essentially a community of volunteers.
From the question on managing geeks (or coders, or cats) yesterday (?), I gather that if you take away the mouse (interesting problem) from the cats (programmers) - they programmers loose interest. Somewhat problematic if your programmers are largely volunteers.
So, let's say you have an OpenSause company. You exist on volunteer programming & documentation, and on service support contracts. Perhaps, to a lesser extent, also on coding paid for features. You can't document too much, or no one will need the support contract. You can't pay for too much code, or you volunteers will feel unappreciated, and fork the code. How do you manage this? Perhaps with a feature bounty?
So, many Open Source companies exist - if only to control the naming rights of their products. Investors see a new buzzword and want to invest. From an open source users standpoint, it's all good: More open source code gets made. From the investors standpoint, it's only good if $$ gets made.
I think it's not such a good deal for many investors, but the investment will get made anyhow - as everyone will want part of the next Zend, Snort, MySql, whatever. However, unless the companies are very careful the investors will find that all their programmers leave for a fork of the project.
Nice of them to cut the price. I would like them to keep the SKU so I didn't have to keep up with anotherone: Although I suppose if they hadn't rebadged it, everyone who bought the 6800 would be pissed at the price cut.
1) Novell (with a bullet) - they used to have like 90% of the SMB server market 2) Word Perfect 3) SuSE 4) Ximian 5) Anything else they have touched, since I'm sure I left a lot out.
The article seems to question raised floor cooling, and state that it is rarely done right at the same time. To paraphrase: 'Raised floors should be 18", and preferably 24 - 30" to accomidate all the crap that goes down there. But that is not possible in buildings not designed for the raised floor.'
Raised floor cooling is built around a couple of assumptions: 1)The amount of cold air pumped into the floor will be adiquate for the heat above it, as well as the vent area to be serviced. 2) There will be a way to pump the hot air out of the ceiling. 3) The room will be relatively sealed.
With a sealed room, Hot air being pulled out of the top, and cold pumped into the correct places below - and a sealed room: Hot air out, cold air in. It is true that the vents near the fan are higher pressure than the ones further away. This just means that since more air will go through, you need fewer of them for equilivant cooling. The key is adiquate AC for the heat, and pumping the heat out to lower the load on the AC (Think 2' or larger exaust fan.).
As the article points out, you need space for laminer flow of the air past all the crud (Network & Power cables, beer, blow up doll,stun gun, etc..)under the floor. This means that the height of the floor should be near the height of an AC stack (think home low flow AC ~18") after removing 6" of that height from the calculation (think big bundle of wires...).
In terms of Moores Law, everything but a Hosting site should not need an air floor since it can now be handled by fewer computers. I remember going to Trump Casino's Data Center. Big room (Think Football Field): Raised Floor. They had very few machines and the place was cold as heck -> Why? Because they had replaced all their giant mainframes with new IBM midrange stuff. More processing power & Less heat. Of course they had to replace a crapload of vented flooring, but I digress.
The Problem with raised flooring is that it is not done correctly (not enough height), or the AC is not upgraded when the heat requirements demand it (too many computers for the thermal load rating of the AC). This is because a) Managment wants raised floor cooling in buildings without the headroom for it, and b) because they want more servers and will be dammed if they think about ancilliaries like AC, they allready did not budget for those damn UPS and Tape backup units...
It's true that the ancilliaries count, but you are not considering the Net Future Value (NFV) of your advice. Not only do you have to purchase everyting in the *replace* case, but the extra cost now, is extra cost. Also, some componants will not speed up significantly: Disks won's spin 2x as fast, and even if they do, they won't saturate a SATA2 bus. IMHO, the last time this oppourtunity showed was early in the Athlon (700MHz - 1.4GHz boards), and in the middle of the Athlon (1.4GHz - 2.8Ghz boards)
2.5 years is the typical life of a business pc: Projecting 2 years out we can expect the low end chip to be $150 and an A64 6000, or 5500x2. Of course, we omit the disk issue as you will fill whatever you have with music and video so the question is moot. You will have to upgrade the memory, but rather than purchasing a new box for $600, you can buy it with your left-over $30 from not pruchasing the a64/3800. (Or the left-over $630 from not getting the 4800)
At any rate, we can expect that a socket 939 machine can be maintained for twice the normal lifespan of the typical PC, simply because the socket will be maintained for a while. The Disk speeding up issue is irrellivant because it is unlikely to saturate a SATA 150 interface, and definately won't fill a SATA2 interface. Memory will speed up, but you will still be able to get more DDR400 for a lower price & dump it in.
When you buy your computer (or motherboard), if you want to keep it useful for a while - buy the one with the socket that you think will be supported in the future. Otherwise, you have limited upgradability: Videocard/Memory only.
Specifically: AMD has said something along the lines of Socket 939 will support x2 chips. Socket 754 will not. Thus, You will be able to buy a low end 939 chip now, and a new one in two years. You will only be able to purchase whatever socket 754 chip they manufacture at the end of the year, as they will likely be phased out. Intel is the same deal: Whatever you buy now, they will change the socket format in a year and stop producing it.
Thus the wise advice would be to buy a socket 939 computer with a slower chip, and upgrade it in a year or two with a dual core.
Sigh, too bad none of the major manufacturers seem to make $700/$800 computers with Socket 939. (New Egg has one for ~$600, but it might as well be white box). My customers still need support if I get hit by a bus; you only get that by purchasing corporate...
Recently, mi staff have informed me about a grave misuse of a seal. Apparently, this website, The Onion, is misusing the Presidential Seal of the United States of Merica. Now, I have not seen this seal - and I hope it's doing well, with all those hurricanes in Florida and whatnot, but to misuse a seal? Now that's nnanimal cruelty.
Now, I have talked to all my friends at Hallyburton about this, and we agree. Seals should be clubbed as babies to be used as coats. If the Seals are not going to be used as coats, they should be allowed to live out their natural lives at Seaworld and the like. You know, preforming tricks for the kids. Ya gotta member the children, they're our most precious resource. But I digress.
This website, The Onion, is misusing the Presidential Seal and it's got to stop. Our staff has sent a letter to The Onion, and they just made fun of us. How terrble is that? Even worse, some people have suggested that the seal be changed at The Onion. That's not good. How would you like it if we changed you?
Anyways, seals are great creatures. Make good coats, preform tricks for kids. Kids important. Onion misusing seals. Onion's bad, make kids cry. Now go out there and tell those bad liberals at The Onion to stop misusing seals and making kids cry.
Open mouth, insert foot. (Stupid slashdot effect. Even the coral cache was down.) Still, a lot of pointy head types won't beleive that this applies to *business* programs.
Without reading the article, I'm going to make some assumptions. (Like "thrashed" means 10% faster.) In which case, this is a case of market management.
Intel can release an underpreforming platform in the server area because "it's validated for a server environent." Otherwise, people can purchase a P4 based server from IBM or some such. By not making noise that the unit has been released, people will assume that it has been on the market for a while - and that's why it is slightly less preforming. It's a case of perception more than fact.
At some point, Intel will have to start preforming. For now, they can get away with promising that they will preform in the near future, and have a competing (not competative) product in the area. AMD may have started taking the consumer chip crown, but the office environment is still aways off.
"I'm sorry, to enter into this bidding process you will need precisely three copies for form WXD-423y. That's form WXD-423-little-Y, little, as opposed to form WXD-423-big=Y."
OK, where do I get the form?
"That particular form is conviently located in our forms distribution center. It's just four exits down the highway, turn left at the toxic waste site, go through the area posted 'Hazardous Radiation' and into the nuclear waste silo. Of course you'll have to dig a bit to get to level 3. Ask for Gloria, she's behind the door marked 'Danger, loose Tiger'. Got that then?"
Yes, of course. But could you tell me down which highway the forms distribution center is located?
"Oh sure, you have form WXD-423 filled out then - let's have it. I can't give you that information without form WXD-423."
Perhaps: more likely everyone "tech savvy" will download video files for the iPod using the same "various methods" that they use currently for music. The mass market will buy. (AKA: The kids will dl with bitx, and the parents will purchase.)
Not really folly, more like bandwidth reality for most consumers.
I suspect that most consumers are closer to low-end DSL than T1. On a saturated T1, a 300MB movie (say 20 minutes, reasonabe US TV type resolution) takes perhaps 40 minutes. I can't ever seem to saturate my link (1.5 down), so assuming that the data transfer is reasonable, lets say 3 hours. (Although, my linux.iso files seem to take longer (yes, they are torrents).
How many people are going to wait 3 hours to get broadcast quality TV? And then how many are going to be happy converting it to a crappy lower iPot resolution?
You may say, what about cable Internet users. While it is true that their is a higher peak rate, everyone gets lagged during peak (before work/school, after work/school/dinner) hours.
The article alludes to executing large numbers of executions simultainiously. Like creating new pathways in the brain that make certain modes of thought more efficient. If it works the shortcuts will avoid many program loops that would normally take processing time and make the trip shorter.
I suppose the whole thing will have to be ACID compliant;)
Keep your mod points: however this requires that I set up the account (each account), then find the correct folders that are associated with each account, and copy them over by hand.
Much easier to say "Import Settings, contacts and email from xyz" Also, it's something I can tell business zombies to do, while copying the account by hand is not.
Slashdot Mirror
Hello Bueler
Hit by the flaw, Bitten by the patch.
Lyrics by me.
I got hit by the flaw, and bitten by the patch
A computer rebuild, a 'driver with a ratchet
It's hit me, it'll be hitting you
How much did you pay for that Sony Doo-Doo?
I Put a music CD in my CD-Drive
Hit "I Accept" to some DRM jive
Now I'm here, waiting for the other shoe
and to make it worse, the music sucked too
Hit by the flaw, bitten by the patch
That company just said bend-over biatch
Bitten by the patch, hit by the flaw
hold on to your hat, 'cause that ain't all
Picked it up this morning from the TV news
Sony got another system that you don't want to use
As if the first one was'nt bad enough, with your computer flubed up
They got a second system that's also bad enough
Hit by the flaw, bitten by the patch
some big CEO needs to take it up the ass
"That's enough now, I'm Tired" - Oppourtunites never knock - The Clash - version where the kid sings it.
Who state (paraphrased) "Our customers don't know how badly we have fucked up their computers, so why should they care that we fucked up their computers so badly that any half compitant thief can steal their personal data, savings, and life?"
Way to go guys.
I used to think that I stopped buying music when I turned 25, because I stopped having disposable income. Turned out that the music just sucked, and the asses putting it out kept trying to give me diseases.
You mis-understood: They meant that Brand-X really sucks.
(No, I don't want to be sued out of my last $.02)
Step 1: Hack Bank & have $rand clients told they are infected; Redirect to fake Norton Site.
Step 2: Take Credit information, infect client PC; churn disk for a while
Step 3: Make ~$5 per client suckered
Step 4: Rent out infected PCs for $$$$$$
Yesterday, when the author of the study was interviewed - I attempted to read the PDF. I could not get it with Mozilla 1.5rc3 and Acrobat reader7. From the authors comments, I had some questions about the methodology.
The Blog Commentary makes several good points about applying "The Windows Way", and configuration management. From the commentary, I can glean that the packages to run on the SUSE box were, shall we say - sub-optimal. Additionally, it appears that the Server was installed with the Kitchen Sink.
While installing the computer with the Kitchen-Sink (TM) options is a bad idea on any Server - it is often done on Windows, and rarely done on Linux. Thus, the patch list summary produced (Windows Patches Linux Patches) would seem questionable on it's face. (No, I can't spell Priema Facia.)
If the systems at download.microsoft.com could have stood up to the slashdotting yesterday, the comment probably would have been modded a 5 here. Since many of us could not get the study to read, it is nice to have it linked.
Good job guys.
I have been running rc2, and it works well but it does have some freezing issues.
0 5/11/17/15rc3-available/ (The release notes blog):
From http://developer.mozilla.org/devnews/index.php/20
* A recent regression that either crashes or breaks certain usages of innerHTML for dynamic applications. (315189/315999)
* A recent regression and most common RC2 crash (316025)
Hopefully, this will resolve most of my issues.
Remember, if you can't wait a day or so for the auto update: Help -> Check for Updates. (If you are running a RC of 1.5)
Kudos for the dev team.
I have an old iRiver H-120. (It's about three years old). My wife hates the interface,butIlove the unit.
1) Connects to CLIENT Win2K; XP boxes via USB as a external HD WITHOUT any drivers
2) FM radio
3) 20GB storage
4) Battery,so I don't have to worry about getting power to "a self powered external case" when I use laptops, or older machines
5) Internal Microphone & recording capability, for when I need to verify details / have a cranky and difficult customer.
6) Marginally larger than an old iPod
The requirement here sounds like it was to be X pages with Y formatting. You can change the formatting on OOo. The formatting should have met the specs.
MSW was not the requirement.
Open Source is largely sucessful when there is a large enough community of quality contributers. They have seen a problem, and are trying to solve it. A company, on the other hand is management directed. The dichotomy of this problem is that an Open Source Company must have "Management" trying to direct what is essentially a community of volunteers.
From the question on managing geeks (or coders, or cats) yesterday (?), I gather that if you take away the mouse (interesting problem) from the cats (programmers) - they programmers loose interest. Somewhat problematic if your programmers are largely volunteers.
So, let's say you have an OpenSause company. You exist on volunteer programming & documentation, and on service support contracts. Perhaps, to a lesser extent, also on coding paid for features. You can't document too much, or no one will need the support contract. You can't pay for too much code, or you volunteers will feel unappreciated, and fork the code. How do you manage this? Perhaps with a feature bounty?
So, many Open Source companies exist - if only to control the naming rights of their products. Investors see a new buzzword and want to invest. From an open source users standpoint, it's all good: More open source code gets made. From the investors standpoint, it's only good if $$ gets made.
I think it's not such a good deal for many investors, but the investment will get made anyhow - as everyone will want part of the next Zend, Snort, MySql, whatever. However, unless the companies are very careful the investors will find that all their programmers leave for a fork of the project.
my $.02
http://theinquirer.net/?article=27493
Nice of them to cut the price. I would like them to keep the SKU so I didn't have to keep up with anotherone: Although I suppose if they hadn't rebadged it, everyone who bought the 6800 would be pissed at the price cut.
List of things that Novell has ruined
1) Novell (with a bullet) - they used to have like 90% of the SMB server market
2) Word Perfect
3) SuSE
4) Ximian
5) Anything else they have touched, since I'm sure I left a lot out.
The article seems to question raised floor cooling, and state that it is rarely done right at the same time. To paraphrase: 'Raised floors should be 18", and preferably 24 - 30" to accomidate all the crap that goes down there. But that is not possible in buildings not designed for the raised floor.'
Raised floor cooling is built around a couple of assumptions: 1)The amount of cold air pumped into the floor will be adiquate for the heat above it, as well as the vent area to be serviced. 2) There will be a way to pump the hot air out of the ceiling. 3) The room will be relatively sealed.
With a sealed room, Hot air being pulled out of the top, and cold pumped into the correct places below - and a sealed room: Hot air out, cold air in. It is true that the vents near the fan are higher pressure than the ones further away. This just means that since more air will go through, you need fewer of them for equilivant cooling. The key is adiquate AC for the heat, and pumping the heat out to lower the load on the AC (Think 2' or larger exaust fan.).
As the article points out, you need space for laminer flow of the air past all the crud (Network & Power cables, beer, blow up doll,stun gun, etc..)under the floor. This means that the height of the floor should be near the height of an AC stack (think home low flow AC ~18") after removing 6" of that height from the calculation (think big bundle of wires...).
In terms of Moores Law, everything but a Hosting site should not need an air floor since it can now be handled by fewer computers. I remember going to Trump Casino's Data Center. Big room (Think Football Field): Raised Floor. They had very few machines and the place was cold as heck -> Why? Because they had replaced all their giant mainframes with new IBM midrange stuff. More processing power & Less heat. Of course they had to replace a crapload of vented flooring, but I digress.
The Problem with raised flooring is that it is not done correctly (not enough height), or the AC is not upgraded when the heat requirements demand it (too many computers for the thermal load rating of the AC). This is because a) Managment wants raised floor cooling in buildings without the headroom for it, and b) because they want more servers and will be dammed if they think about ancilliaries like AC, they allready did not budget for those damn UPS and Tape backup units...
Can we play where in the world are the Bush White House ethics? (Hint, look up Halliburton.)
It's true that the ancilliaries count, but you are not considering the Net Future Value (NFV) of your advice. Not only do you have to purchase everyting in the *replace* case, but the extra cost now, is extra cost. Also, some componants will not speed up significantly: Disks won's spin 2x as fast, and even if they do, they won't saturate a SATA2 bus. IMHO, the last time this oppourtunity showed was early in the Athlon (700MHz - 1.4GHz boards), and in the middle of the Athlon (1.4GHz - 2.8Ghz boards)
Processor-bump Cost-of-bump 2Yr-NFV-of-cost
a64 3800 $180 $215
a64 3800x2 $200 $240
a64 4800x2 $650 $780
2.5 years is the typical life of a business pc: Projecting 2 years out we can expect the low end chip to be $150 and an A64 6000, or 5500x2. Of course, we omit the disk issue as you will fill whatever you have with music and video so the question is moot. You will have to upgrade the memory, but rather than purchasing a new box for $600, you can buy it with your left-over $30 from not pruchasing the a64/3800. (Or the left-over $630 from not getting the 4800)
At any rate, we can expect that a socket 939 machine can be maintained for twice the normal lifespan of the typical PC, simply because the socket will be maintained for a while. The Disk speeding up issue is irrellivant because it is unlikely to saturate a SATA 150 interface, and definately won't fill a SATA2 interface. Memory will speed up, but you will still be able to get more DDR400 for a lower price & dump it in.
Just take them and the other crap out;)
When you buy your computer (or motherboard), if you want to keep it useful for a while - buy the one with the socket that you think will be supported in the future. Otherwise, you have limited upgradability: Videocard/Memory only.
Specifically: AMD has said something along the lines of Socket 939 will support x2 chips. Socket 754 will not. Thus, You will be able to buy a low end 939 chip now, and a new one in two years. You will only be able to purchase whatever socket 754 chip they manufacture at the end of the year, as they will likely be phased out. Intel is the same deal: Whatever you buy now, they will change the socket format in a year and stop producing it.
Thus the wise advice would be to buy a socket 939 computer with a slower chip, and upgrade it in a year or two with a dual core.
Sigh, too bad none of the major manufacturers seem to make $700/$800 computers with Socket 939. (New Egg has one for ~$600, but it might as well be white box). My customers still need support if I get hit by a bus; you only get that by purchasing corporate...
Dear mi fellow Mericans.
Recently, mi staff have informed me about a grave misuse of a seal. Apparently, this website, The Onion, is misusing the Presidential Seal of the United States of Merica. Now, I have not seen this seal - and I hope it's doing well, with all those hurricanes in Florida and whatnot, but to misuse a seal? Now that's nnanimal cruelty.
Now, I have talked to all my friends at Hallyburton about this, and we agree. Seals should be clubbed as babies to be used as coats. If the Seals are not going to be used as coats, they should be allowed to live out their natural lives at Seaworld and the like. You know, preforming tricks for the kids. Ya gotta member the children, they're our most precious resource. But I digress.
This website, The Onion, is misusing the Presidential Seal and it's got to stop. Our staff has sent a letter to The Onion, and they just made fun of us. How terrble is that? Even worse, some people have suggested that the seal be changed at The Onion. That's not good. How would you like it if we changed you?
Anyways, seals are great creatures. Make good coats, preform tricks for kids. Kids important. Onion misusing seals. Onion's bad, make kids cry. Now go out there and tell those bad liberals at The Onion to stop misusing seals and making kids cry.
Good night, and God Bless you.
Yer President
Open mouth, insert foot. (Stupid slashdot effect. Even the coral cache was down.) Still, a lot of pointy head types won't beleive that this applies to *business* programs.
mmmmmm, fungus - ahhhhhh
Without reading the article, I'm going to make some assumptions. (Like "thrashed" means 10% faster.) In which case, this is a case of market management.
Intel can release an underpreforming platform in the server area because "it's validated for a server environent." Otherwise, people can purchase a P4 based server from IBM or some such. By not making noise that the unit has been released, people will assume that it has been on the market for a while - and that's why it is slightly less preforming. It's a case of perception more than fact.
At some point, Intel will have to start preforming. For now, they can get away with promising that they will preform in the near future, and have a competing (not competative) product in the area. AMD may have started taking the consumer chip crown, but the office environment is still aways off.
$.02
"I'm sorry, to enter into this bidding process you will need precisely three copies for form WXD-423y. That's form WXD-423-little-Y, little, as opposed to form WXD-423-big=Y."
OK, where do I get the form?
"That particular form is conviently located in our forms distribution center. It's just four exits down the highway, turn left at the toxic waste site, go through the area posted 'Hazardous Radiation' and into the nuclear waste silo. Of course you'll have to dig a bit to get to level 3. Ask for Gloria, she's behind the door marked 'Danger, loose Tiger'. Got that then?"
Yes, of course. But could you tell me down which highway the forms distribution center is located?
"Oh sure, you have form WXD-423 filled out then - let's have it. I can't give you that information without form WXD-423."
Perhaps: more likely everyone "tech savvy" will download video files for the iPod using the same "various methods" that they use currently for music. The mass market will buy. (AKA: The kids will dl with bitx, and the parents will purchase.)
Not really folly, more like bandwidth reality for most consumers.
.iso files seem to take longer (yes, they are torrents).
I suspect that most consumers are closer to low-end DSL than T1. On a saturated T1, a 300MB movie (say 20 minutes, reasonabe US TV type resolution) takes perhaps 40 minutes. I can't ever seem to saturate my link (1.5 down), so assuming that the data transfer is reasonable, lets say 3 hours. (Although, my linux
How many people are going to wait 3 hours to get broadcast quality TV? And then how many are going to be happy converting it to a crappy lower iPot resolution?
You may say, what about cable Internet users. While it is true that their is a higher peak rate, everyone gets lagged during peak (before work/school, after work/school/dinner) hours.
my $.02
The article alludes to executing large numbers of executions simultainiously. Like creating new pathways in the brain that make certain modes of thought more efficient. If it works the shortcuts will avoid many program loops that would normally take processing time and make the trip shorter.
I suppose the whole thing will have to be ACID compliant;)
Keep your mod points: however this requires that I set up the account (each account), then find the correct folders that are associated with each account, and copy them over by hand.
Much easier to say "Import Settings, contacts and email from xyz" Also, it's something I can tell business zombies to do, while copying the account by hand is not.