YOU CAN"T JUST BURY MATERIAL IN DANGER OF CRITICALITY.
Well, you could - but by not cooling the nuclear reaction, you raise the risk of a larger catastrophic failure. You have a thousand tons of unconfined fuel rods in cooling pools which could lead to a fire and larger release of radioactive materials. By cooling and watering the materials you not only slow criticality (water and boron), but you also prevent particles from leaving the effected area.
Chernobly blew apart most of the critical material and a fire raged for a few days afterwards. Allowing an uncontrolled reaction to take place in 3-4 reactor pools would arguably create a similar or possibly worse situation.
In effect this is a "controlled meltdown" - it will take months (years?) to reach a stage before they can manage the problem with great confidence.
I was at a baby bell in the 90's, just after and during the time when these labs were getting torn down. After struggling for years to generate high income quick-hit research, the budgets of these labs were quickly transitioned into IT and software development in an effort to generate service profits and enlarge the short-term profits. The baby bells built caller-id, call waiting and bigger billing systems. Excess R&D was given to Universities and funded many academic labs.
So developers should probably be thankful for the opportunities really... It's likely that the demise of pure R&D was a big contributor to the growth of PC hardware, software and internet development.
This really isn't a POTS type switching system anyway - it more closely resembles a protocol splitter. You get an IP gateway for cellular data, SS7 over ATM for voice, and perhaps an IP gateway for SMS messaging. Of course the real meat of the operation is the BILLING SYSTEM!
Well NASA has done similar things before - for instance the Mars Phoenix reused several components from previous missions (including the failed Mars Polar Lander).
In general I agree with what you're saying - though likely many mission scientist would raise concerns over too much generic hardware. There's issues with weight, mass distribution, power management and of course congress.
A chest X-Ray only happens a few times in one's life. A long prolonged exposure to environment radiation is likely much worse. At current levels we'll only be killing a handful of people. As long as the reactors keep churning out radiation, it will continue to ratchet up the death count one by one.
I realize that lots of people die from smoking, heart disease, auto accidents and lightning... my only point is that the accident is not zero consequence.
Just a small comparison between New Zealand and Japan here: 1. Local sources of natural energy, including petrol(20Tbpd), natural gas(1.5bcf), hydro(25B kWh), sun, some tide, decent wind. 2. Population of 4 million
Japan: 1. Few natural sources of energy, little petrol(6Tbpd) or gas(2bcf). Good hydroelectric(80B kWh) but completely exerted. Poor areas for tidal generation. Low sun, decent wind. 2. Population of 127 million.
There is a stark difference between Japan and NZ, both in terms of population, industrial capacity and availability of resources. By comparison, per capita New Zealanders have a luxurious energy surplus. It is true that New Zealand is a net energy importer (like Japan), but (IMHO) part of the basis for that decision is to reserve existing oil reserves as a strategic hedge against rising oil prices.
Perhaps one day we can all live in the same situation as New Zealand, but designs for tidal, solar and wind power are not currently enough to provide much more than a basic level of service for Japan, much less an industrial economy.
Besides - any wall in Arabia could easily be spray-painted with this message and photographed... spray paint is cheap. I don't see the point in photoshopping such an image with little long-term significance.
I had the same issue - but now I feel exactly the opposite. Fewer menu bars means more room for applications and (for me at least) lest confusion when switching between apps.
Give the boy a Mod - absolutely correct interpretation IMHO.
I disagree with the Federal Reserve Act (I believe the bank should be owned by the people, not private) - but given our history, it's probably inevitable that given the attitudes towards the law that the same thing would have happened.
2600 and the EFF completely screwed that one up... Felton had a better case and could have published his academic paper for a challenge, and it would have won. Instead 2600 just appeared to be giving away the dvd farm with the decss utility, and Felton lost the "academically chilled" lawsuit. Ugh.
That's because it's one of the oldest universities in the world... from 1088. Dante and Copernicus were alumni I think. They're certainly lost their luster in the past couple of hundred years, but who knows?
yes, it'll matter because the back end is still HTML. And not everything that creates and renders HTML is dreamweaver, firefox or iexplorer. And while management practices do not matter, specifications and implementations DO matter. Most especially, for those that rely on accuracy. product comparisons, and compatibility.
Have you handled 300 million users lately? Just the backend storage scaling itself probably eats a hundred engineers... then there's the code performance engineering, php compiler and memcached wranglers... there's another 100 engineers. And of course there's the network engineers! And the Apache engineers(50) and the cable engineers, the customer support engineers... OH and the social engineers!!
That leaves about... (click click click...) 4 engineers to work on the interface code.
When I worked as a data archivist about a dozen years ago, we routinely recovered data from oil seismic recordings. Some of the oldest recordings we recovered were made on 1" tape, originally recorded on TI tape drives (GSI TIAC machines). These spools weighed about 18lbs... don't drop em'.
For it's time it must have been fairly advanced, as the data was 8 channel, 8 bit sampling @ 100Hz...
IMHO the biggest problem with these multi-core chips is the lock latency. Locking in heap all works great, but a shared hw register of locks would save a lot of cache coherency and MMU copies.
A 1024 slot register with instruction support for mutex and read-write locks would be fantastic.
I'm developing 20+Gbps applications - we need fast locks and low latency. Snap snap!!!
The facts are that bad things happen, and we should be minimizing risk using background checks, personal interviews and smarter policy. We should be changing times and procedures to minimize timing attacks. Breaking federal law should not be standard policy.
We should also be brave enough to understand that we take a risk when we walk, drive, swim, surf, eat, drink and fly. The horrible, ugly truth is that bad things happen no matter how much we do to avoid it.
If you look at the beginning of the video, you'll notice there are two separate views of the launch. The bottom of the contrails and the arcs are significantly different - where definitely proves that whatever it was, was a near vertical launch.
Java has a huge tool base and lots of great development already done, more developers and a larger platform base. But, IMHO C# is a cleaner and more consistent language. Delegates are nice at times as well, something we're used in messaging and protocol libraries with great success.
Slashdot Mirror
Good job, those are MUCH better.
Too many repetitive letters to be true OTP. There are several repetitive sequences. It appears to be more akin to a sort of compression to my eyes...
YOU CAN"T JUST BURY MATERIAL IN DANGER OF CRITICALITY.
Well, you could - but by not cooling the nuclear reaction, you raise the risk of a larger catastrophic failure. You have a thousand tons of unconfined fuel rods in cooling pools which could lead to a fire and larger release of radioactive materials. By cooling and watering the materials you not only slow criticality (water and boron), but you also prevent particles from leaving the effected area.
Chernobly blew apart most of the critical material and a fire raged for a few days afterwards. Allowing an uncontrolled reaction to take place in 3-4 reactor pools would arguably create a similar or possibly worse situation.
In effect this is a "controlled meltdown" - it will take months (years?) to reach a stage before they can manage the problem with great confidence.
I was at a baby bell in the 90's, just after and during the time when these labs were getting torn down. After struggling for years to generate high income quick-hit research, the budgets of these labs were quickly transitioned into IT and software development in an effort to generate service profits and enlarge the short-term profits. The baby bells built caller-id, call waiting and bigger billing systems. Excess R&D was given to Universities and funded many academic labs.
So developers should probably be thankful for the opportunities really... It's likely that the demise of pure R&D was a big contributor to the growth of PC hardware, software and internet development.
This really isn't a POTS type switching system anyway - it more closely resembles a protocol splitter. You get an IP gateway for cellular data, SS7 over ATM for voice, and perhaps an IP gateway for SMS messaging. Of course the real meat of the operation is the BILLING SYSTEM!
Well NASA has done similar things before - for instance the Mars Phoenix reused several components from previous missions (including the failed Mars Polar Lander).
In general I agree with what you're saying - though likely many mission scientist would raise concerns over too much generic hardware. There's issues with weight, mass distribution, power management and of course congress.
A chest X-Ray only happens a few times in one's life. A long prolonged exposure to environment radiation is likely much worse. At current levels we'll only be killing a handful of people. As long as the reactors keep churning out radiation, it will continue to ratchet up the death count one by one.
I realize that lots of people die from smoking, heart disease, auto accidents and lightning... my only point is that the accident is not zero consequence.
Just a small comparison between New Zealand and Japan here:
1. Local sources of natural energy, including petrol(20Tbpd), natural gas(1.5bcf), hydro(25B kWh), sun, some tide, decent wind.
2. Population of 4 million
Japan:
1. Few natural sources of energy, little petrol(6Tbpd) or gas(2bcf). Good hydroelectric(80B kWh) but completely exerted. Poor areas for tidal generation. Low sun, decent wind.
2. Population of 127 million.
There is a stark difference between Japan and NZ, both in terms of population, industrial capacity and availability of resources. By comparison, per capita New Zealanders have a luxurious energy surplus. It is true that New Zealand is a net energy importer (like Japan), but (IMHO) part of the basis for that decision is to reserve existing oil reserves as a strategic hedge against rising oil prices.
Perhaps one day we can all live in the same situation as New Zealand, but designs for tidal, solar and wind power are not currently enough to provide much more than a basic level of service for Japan, much less an industrial economy.
Clearly I have defeated this earthworm with my words – imagine what I would have done with my fire breathing first!
Besides - any wall in Arabia could easily be spray-painted with this message and photographed... spray paint is cheap. I don't see the point in photoshopping such an image with little long-term significance.
I had the same issue - but now I feel exactly the opposite. Fewer menu bars means more room for applications and (for me at least) lest confusion when switching between apps.
Give the boy a Mod - absolutely correct interpretation IMHO.
I disagree with the Federal Reserve Act (I believe the bank should be owned by the people, not private) - but given our history, it's probably inevitable that given the attitudes towards the law that the same thing would have happened.
2600 and the EFF completely screwed that one up... Felton had a better case and could have published his academic paper for a challenge, and it would have won. Instead 2600 just appeared to be giving away the dvd farm with the decss utility, and Felton lost the "academically chilled" lawsuit. Ugh.
Here's the same video with English subtitles
Click on CC mark to show subtitles.
That's because it's one of the oldest universities in the world... from 1088. Dante and Copernicus were alumni I think. They're certainly lost their luster in the past couple of hundred years, but who knows?
On what planet is a bathtub thought of as furniture? Strange Virginians...
Howard Moskowitz - Spaghetti Sauce!
yes, it'll matter because the back end is still HTML. And not everything that creates and renders HTML is dreamweaver, firefox or iexplorer. And while management practices do not matter, specifications and implementations DO matter. Most especially, for those that rely on accuracy. product comparisons, and compatibility.
Have you handled 300 million users lately? Just the backend storage scaling itself probably eats a hundred engineers... then there's the code performance engineering, php compiler and memcached wranglers... there's another 100 engineers. And of course there's the network engineers! And the Apache engineers(50) and the cable engineers, the customer support engineers... OH and the social engineers!!
That leaves about... (click click click...) 4 engineers to work on the interface code.
When I worked as a data archivist about a dozen years ago, we routinely recovered data from oil seismic recordings. Some of the oldest recordings we recovered were made on 1" tape, originally recorded on TI tape drives (GSI TIAC machines). These spools weighed about 18lbs... don't drop em'.
For it's time it must have been fairly advanced, as the data was 8 channel, 8 bit sampling @ 100Hz...
IMHO the biggest problem with these multi-core chips is the lock latency. Locking in heap all works great, but a shared hw register of locks would save a lot of cache coherency and MMU copies.
A 1024 slot register with instruction support for mutex and read-write locks would be fantastic.
I'm developing 20+Gbps applications - we need fast locks and low latency. Snap snap!!!
The facts are that bad things happen, and we should be minimizing risk using background checks, personal interviews and smarter policy. We should be changing times and procedures to minimize timing attacks. Breaking federal law should not be standard policy.
We should also be brave enough to understand that we take a risk when we walk, drive, swim, surf, eat, drink and fly. The horrible, ugly truth is that bad things happen no matter how much we do to avoid it.
The threat of public stoning grows daily in Ye Grande Olde Britain!
If you look at the beginning of the video, you'll notice there are two separate views of the launch. The bottom of the contrails and the arcs are significantly different - where definitely proves that whatever it was, was a near vertical launch.
Java has a huge tool base and lots of great development already done, more developers and a larger platform base. But, IMHO C# is a cleaner and more consistent language. Delegates are nice at times as well, something we're used in messaging and protocol libraries with great success.