It's to prevent it from collecting dust, which would change the weight.. err, mass. Corrosion prevention might be a goal, too (yes, the alloy is corrosion resistant, but not entirely corrosion proof.) I don't think they're worried about evaporation, though (all substances outgas to a certain degree, some more slowly than others)
I just wrote a letter to my insurance company regarding them, and I would urge everyone here to do the same.
To whom it may concern:
This isn't really a complaint, but I'd like to make sure that you do not do business with ChoicePoint. With the recent scandal (Congress is now getting involved) over the release of private data to fictitious businesses and individuals, I would prefer that any of the information that you store on me is not and will not be transferred to their systems in the future.
I would also prefer (but realize it'll probably be impossible to guarantee) that they destroy any data they currently have on myself, and other policyholders.
There's a lot of energy in a Li-Ion battery, and when it gets an internal short (or really overheated) it's usually bad for your homeowner's policy. Or pants, depending on the device.
South Korea is about the size of Indiana. If the US were to spend $11 billion for wiring Indiana, they'd have a pretty good internet infrastructure, too.
Also, with a population of 48.5 million people, Korea is pretty densely populated. Compare that to Indiana, which at 6.2 million people, is fairly lightly populated. It wouldn't be cost effective to wire the entire state for broadband with the population density it currently has.
Now that a weakness has been shown for SHA-1, has the same analysis been done for SHA-256 & 512?
Admittedly, dropping 2^11 values off a 256-bit hash doesn't reduce the time to find a collision that much, but perhaps for the versions other than SHA-1, it's more than 2^11?? I wouldn't want to change algorithms from one that has a known weakness to one which has an even bigger unknown weakness.
So I'll change once the other SHA versions have been shown to be free of this weakness.
As the machines extrude your house, it'll be pretty easy to put in horizonatal wiring & plumbing runs -- just lay them in the damp concrete before putting the next layer on top.
I wonder how they'll handle the vertical runs, like go from the water line up to the kitchen & baths? Also, every building code in the US requires a vent at the top of each plumbing stack, so for every bathroom that's not on top of another bathroom, you need a separate vent.
If you've got the money and the need for a SCM tool like Perforce, you should also be looking at Borland Star Team (comes with defect tracking utility) and Clearcase.
If costs like $1000 per seat scare you off, and/or you don't have a need for planet-wide team development, then maybe Subversion would be suitable.
FYI: the 5-planet Klemperer Rosette used as a plot device by Larry Niven for the Puppeteer's home worlds has been shown to be unstable:
http://burtleburtle.net/bob/physics/kempler.html
(warning, contains java applets which will probably freeze up Firefox)
Reading the article, it reminds me of the typical mainframe architecture, where you have a central supervisory CPU, but most of the specialized work is done by the channel processors.
In the Cell, the main PPC CPU appears to identify a piece of work that needs to be done, schedules it to run on a SPE, uploads the code snippet to the SPE's LS via DMA transfer, and then goes off and does something else worthwhile while the SPE munches on it. I presume there's an interrupt mechanism to let the PPC know that a SPE has some results to return.
Compiler writers ought to be able to handle this new architecture well enough -- it's sort of like the current CPU/GPU split, where you've got the main program running on the system CPU, and specialized graphical transform programlets running on the GPU. There may need to be macros or code section identifiers in the source to let the compiler know which to target for that bit of code.
Obviously, this is just the first iteration of the Cell processor. I can see them widening the SPE from single precision to double precision (for the scientific market -- the game market probably doesn't need it), and going to a multi-core design to reduce the die size.
Y'all might be interested in reading Wolfgang Flur's book on his Kraftwerk years:
Kraftwerk: I Was a Robot
ISBN: 1860744176
Basically, (according to Wolfgang), he never received any royalties from the songs, because he was regarded as an employee of the band, and was on salary. Interestingly, one of the last chapters reveals that much of the Kraftwerk sound was the result of producer Conny Plank (who also worked with Brian Eno on the first Devo album).
If they plan on offering reliable delivery, they'll need a place to store messages until the recepient is able to receive them. I wonder what they'll use for this -- At the reliability levels that Wall Street demands, I don't think something like MySQL is up to it.
Assuming a well-written anti-virus product, the performance hit would scale linearly with each new family of virii released into the wild. More viruses in existence (even if they're not attacking you at the moment) means slower PCs because the anti-virus code has more to check before letting you do something productive.
Sure, it was cooperatively multi-tasked, but for the GUI only. It still was a step up from anything else (including MacOS) because you had the ability to launch long-running tasks in another thread or process, and your GUI stayed responsive.
PMMail, for example, would gray-out certain actions while downloading new mail. You could still do other tasks while this was going on in the background. Can't do that in Outlook.
As a result of my learning how to (more or less correctly;-)) write multi-threaded code, I found myself at a significant advantage to all the Win 3.1 developers when WinNT came out. They were all freaking out over semaphores & mutexes (ie. not using them where they should have), when OS/2 developers were saying "So what? You *have* to use them in this situation."
That was because the message loop ran in a single thread within the OS. If one app stopped working while reading messages, all the other apps would freeze. The delay in restarting was from a watchdog thread that would kick the message pump back into life.
The rule of thumb for PM apps was 1/10th of a second. That's how long you had to do something before you needed to call a message function. As a result, most OS/2 apps were significantly multi-threaded out of necessity. Compare that with your typical Win32 app which is almost always single-threaded.:-(
Slashdot Mirror
Aren't all new laws required to be published in the Federal Register?
Chip H.
It's to prevent it from collecting dust, which would change the weight.. err, mass. Corrosion prevention might be a goal, too (yes, the alloy is corrosion resistant, but not entirely corrosion proof.) I don't think they're worried about evaporation, though (all substances outgas to a certain degree, some more slowly than others)
It's nested in several jars for redundancy.
Chip H.
Chip H.
Balter is a fag
Dude, have you seen the chick he's seeing?
Chip H.
What about reducing the chance of fires?
There's a lot of energy in a Li-Ion battery, and when it gets an internal short (or really overheated) it's usually bad for your homeowner's policy. Or pants, depending on the device.
Chip H.
South Korea is about the size of Indiana. If the US were to spend $11 billion for wiring Indiana, they'd have a pretty good internet infrastructure, too.
Also, with a population of 48.5 million people, Korea is pretty densely populated. Compare that to Indiana, which at 6.2 million people, is fairly lightly populated. It wouldn't be cost effective to wire the entire state for broadband with the population density it currently has.
Chip H.
Could be worse I suppose -- it could have been the friendly folks from Planet Kricket with their very small bomb.
Chip H.
It is now :-(
Chip H.
Now that a weakness has been shown for SHA-1, has the same analysis been done for SHA-256 & 512?
Admittedly, dropping 2^11 values off a 256-bit hash doesn't reduce the time to find a collision that much, but perhaps for the versions other than SHA-1, it's more than 2^11?? I wouldn't want to change algorithms from one that has a known weakness to one which has an even bigger unknown weakness.
So I'll change once the other SHA versions have been shown to be free of this weakness.
Chip H.
Maybe he should listen to the parents -- they're his customers. And not satisfying them could cost him his job.
Chip H.
They just set the evil bit.
Chip H.
Do a whois. It's owned by Wraith Enterprises in Austin, TX.
Chip H.
Mine is localhost.com
Those guys must be making a killing from people hitting ctrl-enter by mistake.
Chip H.
{Jedi hand wave}
These are not the disks you're looking for.
Chip H.
As the machines extrude your house, it'll be pretty easy to put in horizonatal wiring & plumbing runs -- just lay them in the damp concrete before putting the next layer on top.
I wonder how they'll handle the vertical runs, like go from the water line up to the kitchen & baths? Also, every building code in the US requires a vent at the top of each plumbing stack, so for every bathroom that's not on top of another bathroom, you need a separate vent.
Chip H.
Not really. The ACLU focuses on supporting the 1st & 4th amendments, while the NRA focuses on the 2nd.
If the membership of the ACLU wasn't so rabidly anti-gun, I'd join them, too.
Chip H.
If you've got the money and the need for a SCM tool like Perforce, you should also be looking at Borland Star Team (comes with defect tracking utility) and Clearcase.
If costs like $1000 per seat scare you off, and/or you don't have a need for planet-wide team development, then maybe Subversion would be suitable.
Chip H.
1. Make the airlocks compatible with each other and the NASA stuff.
2. Make the Oxygen and Nitrogen fittings standard, and not mechanically interchangable.
3. Develop the equivalent to the Guard frequency (international rescue radio channel), but for spacecraft.
Chip H.
FYI: the 5-planet Klemperer Rosette used as a plot device by Larry Niven for the Puppeteer's home worlds has been shown to be unstable:
http://burtleburtle.net/bob/physics/kempler.html
(warning, contains java applets which will probably freeze up Firefox)
Chip H.
Reading the article, it reminds me of the typical mainframe architecture, where you have a central supervisory CPU, but most of the specialized work is done by the channel processors.
In the Cell, the main PPC CPU appears to identify a piece of work that needs to be done, schedules it to run on a SPE, uploads the code snippet to the SPE's LS via DMA transfer, and then goes off and does something else worthwhile while the SPE munches on it. I presume there's an interrupt mechanism to let the PPC know that a SPE has some results to return.
Compiler writers ought to be able to handle this new architecture well enough -- it's sort of like the current CPU/GPU split, where you've got the main program running on the system CPU, and specialized graphical transform programlets running on the GPU. There may need to be macros or code section identifiers in the source to let the compiler know which to target for that bit of code.
Obviously, this is just the first iteration of the Cell processor. I can see them widening the SPE from single precision to double precision (for the scientific market -- the game market probably doesn't need it), and going to a multi-core design to reduce the die size.
Chip H.
Y'all might be interested in reading Wolfgang Flur's book on his Kraftwerk years:
Kraftwerk: I Was a Robot
ISBN: 1860744176
Basically, (according to Wolfgang), he never received any royalties from the songs, because he was regarded as an employee of the band, and was on salary. Interestingly, one of the last chapters reveals that much of the Kraftwerk sound was the result of producer Conny Plank (who also worked with Brian Eno on the first Devo album).
Chip H.
If they plan on offering reliable delivery, they'll need a place to store messages until the recepient is able to receive them. I wonder what they'll use for this -- At the reliability levels that Wall Street demands, I don't think something like MySQL is up to it.
Chip H.
Assuming a well-written anti-virus product, the performance hit would scale linearly with each new family of virii released into the wild. More viruses in existence (even if they're not attacking you at the moment) means slower PCs because the anti-virus code has more to check before letting you do something productive.
Chip H.
Sure, it was cooperatively multi-tasked, but for the GUI only. It still was a step up from anything else (including MacOS) because you had the ability to launch long-running tasks in another thread or process, and your GUI stayed responsive.
;-)) write multi-threaded code, I found myself at a significant advantage to all the Win 3.1 developers when WinNT came out. They were all freaking out over semaphores & mutexes (ie. not using them where they should have), when OS/2 developers were saying "So what? You *have* to use them in this situation."
PMMail, for example, would gray-out certain actions while downloading new mail. You could still do other tasks while this was going on in the background. Can't do that in Outlook.
As a result of my learning how to (more or less correctly
Chip H.
That was because the message loop ran in a single thread within the OS. If one app stopped working while reading messages, all the other apps would freeze. The delay in restarting was from a watchdog thread that would kick the message pump back into life.
:-(
The rule of thumb for PM apps was 1/10th of a second. That's how long you had to do something before you needed to call a message function. As a result, most OS/2 apps were significantly multi-threaded out of necessity. Compare that with your typical Win32 app which is almost always single-threaded.
Chip H.