1 - How long will the melted down core remnants needs to water to be applied? Can the corium still sustain a nuclear chain reaction if it were exposed?
2 - Whats would occur if water were interrupted at this point? (They called it cold shutdown a year ago but sources seem to conflict)
3 - How long will water need to be applied to the spent fuel ponds? From my understanding the fuel above reactor 4 is somewhat precarious since the building was compromised during the original explosions. Would these fuel rods ignite without water? Is there a real criticality danger if removal does not go exactly as planned? (Wikipedia seems to say criticality in fuel pools is a low-probability event under normal conditions)
4 - Whats your worst case scenario?
Just trying to find some basic scientific answers here, hoping someone can provide insight.
They found that people who began using pot earlier in life and used it most frequently over the years experienced an average decline of eight IQ points by the time they turned 38.
I'm betting most people lose at least eight IQ points by the time they turn 38.
That's why the mathematicians who do the groundbreaking work mostly are younger than 38. There are still brilliant mathematicians older than that, but they're not the ones who are doing the most important new work.
Actually in some ways it would be really really exciting and almost certainly a really good thing in the long run, because there are a lot of important, currently-intractable problems that become tractable if P=NP.
Proving that P=NP doesn't make anything tractable, unless you use the ridiculous definition where tractable is the same as polynomial time. What would have practical applications is if someone finds a very fast algorithm for solving all the NP problems. Whether P=NP is not really very much related to the question of whether such an algorithm exists. ML has exponential-time type checking, yet ML compiles don't take that long. Polynomial time is not the same as practical - it fails in both directions.
Factoring is in NP... If P=NP, factoring is in P...
You can't compare symmetric key lengths (based on AES) with RSA modulus sizes. An extra bit in a symetric key gives you alot more security than an extra bit in the RSA key..
Perhaps it needs more structure? e.g. a 10mx10m region shares the same two words and then the third word acts as a reference into that array of 100 points...
I was under the impression Big-O implies the existance of a constant c, for all x > c, f(x) > g(x) where f(x) is the function your bounding it by and g(x) is the function you're trying to describe..
Hence, its just saying "sooner or later", this will always be a bound...
There is pretty much nothing you can do by hand that puppet can't also do - and often it takes just as much time to update a single puppet config file and run the puppet update process as it would be to ssh into the server and make the manual change.
Another advantage is what might go into traditional documentation is now just a puppet configuration.. Oh, fuck, this server crashed? Just roll another in 5 minutes... Who cares about the old one..
And this is the flaw in your argument. There seems to be some assumption that if it's not under control of Puppet or Chef then it's manual. This is completely untrue. Any competent admin automates their administration. I've been doing it for more than a decade.
Second it's not the host OS and host configuration that makes the servers distinct. It's the data. You can't automate ten years worth of data entry and workflow modules. I suppose it would be unfair of me to hold against you the fact that you don't know anything about my operations, but we're not an internet based company. We're doing stuff other than serving up a bunch of vanity gopro videos. We have several large data centers but we also have hundreds of offices around the world and those offices have their own IT infrastructure. Anyone can stand up a server in 10 minutes in their data center. How long will it take you to stand one up Chengdu given that your primary data centers are in the US and Europe and your network line to the remote facility is 512Kb/s?
The absurdity of the proponents of CFengine, Puppet, Chef, et. al. is that they assume no one has ever solved these problems before. What problems that I have are these products going to solve for me? The emphasis is on "problems that I have". It's not sufficient to tell me what a product does, it's whether it solves my problems.
You are right, there is nothing you can do with puppet that you can't do with SSH, and 10 years ago things like puppet didn't even exist so it makes total sense for you to be in the situation you're in and it wouldn't make alot of sense for you to switch just for the sake of using puppet.
But it's 2013, if you're starting off new - why would you roll your own when many solutions already exist that have been thoroughly tested and extended to have a rich feature set that you probally wouldn't have time to develop as a day-to-day dev op. Furthermore, Puppet allows for this idea of modules that people can write generic versions of "apache" or whatever and often times you don't even have to write configuration systems yourself but instead you can just clone it off github and customize it to your liking..
Your question about standing up servers is silly - why would a more manual solution be impacted differently than a puppet solution based on in-bound bandwidth? Puppet allows for client/server architecture and if bandwidth was your big concern, you could set up a local puppet machine in Chengdu and build servers in that data center based on that...
I worked in a largeish datacenter in 2002 and wrote alot of SSH scripts to manage those servers - it works but its tedious. The benefits of using something like puppet is enormous.. The company I work for now used to employ a full time sysadmin - now the devs just update puppet as we need and it hardly impacts our workloads given how easy it is for us to maintain...
That was a pretty poor review. Giving a summary of the table of contents isn't a review. Additionally it doesn't seem like they recognize that devops and duplicative administration don't fit with a lot of data processing models. There are many organizations that have servers that have a distinct purpose and it doesn't make sense to envision them as just another clone system in "the cloud".
This is why puppet has a very strong inheritance system...
We have it broken down as generic server (2 factor/LDAP configs, nagios configs, etc) and then apache_servers which build out the basic web infrastructure and then more specialized configs for one-off speicalized servers... (admin server versus production web servers)
There is pretty much nothing you can do by hand that puppet can't also do - and often it takes just as much time to update a single puppet config file and run the puppet update process as it would be to ssh into the server and make the manual change.
Another advantage is what might go into traditional documentation is now just a puppet configuration.. Oh, fuck, this server crashed? Just roll another in 5 minutes... Who cares about the old one..
1. jQuery core is hardly bloated, its 32k.. If you are willing to drop support for older IE, you can use jQuery 2.0 which is even more streamlined than its ever been.
2. Animations are not part of jQuery, they are part of jQuery UI which is a totally separate library and which I agree, sucks.
Is much more maintainable to me than several lines of new xmlhttprequiest()... blah blah blah... every time you need to make an ajax call...
4. Jquery has lot of powerful stuff that lets you write less code much of the time such as.on().. Much of the bad javascript I come across is from people who are trying to write it all themselves and have onclick handlers hard coded into tags in a giant unmaintainable mess. Unobtrusive Javascript is for the win and you'll save yourself alot of headache using jQuery to write it.
You'd be crazy to use an inefficient and over-weight library like jQuery anyway. Adding jQuery mobile to that is just asking for trouble.
Let's face it: jQuery has long outlived it's utility. It's not even viable for dealing with old browser compatibility issues on the Desktop.
Just learn JavaScript. Your users will thank you. I'll bet that you'll even ultimately save time and effort as you'll spend less time trying to squeeze acceptable performance out of Resig's cludge -- and less time trying to debug the nasty one-liners you're forced to write to get those tiny improvements.
This is dumb for a variety of reasons. jQuery lets you abstract away a ton browser inconsistencies. It also makes you alot more productive b/c you don't have to constantly event wheels...JS by itself is extremely tedious syntax wise . (do you really like document.getElementById riddling your code to the point of unreadability? I'm sure you'd say oh, i'll just write a helper. Well congrats, there you go inventing wheels)
Some of the worst code I run across on the web always seems to be the guy that insists on doing things with pure javascript and he has tons of onclick handlers directly on tags and all sorts of other crap which makes sites completely unmaintainable...
I've dealt with similiar situations in my professional career. Rackspace's DDOS protection isn't worth it, after 3Mbps, they null routed our box because the size of the attack was so large that it was saturating their uplink capacity...
Prolexic has a cool approach, you proxy your site through them (either web proxy or they can annouce BGP routes for you) and they have massive datacenters that do nothing but scrub packets for you.
The downside is their service is very very expensive ($60k+ a year)
If you're building any sort of complicated website these days, you will use alot of jQuery.. Do you really want to go write a custom ajax handler? why bother..
Plus, using jQuery allows you to leverage tons of other pre-written libraries which were all written on top of jQuery and will avoid alot of cross-browser bugs and repeated code..
Slashdot Mirror
Its relevant as it highlights the effect of the underlying gerrymandering...
1 - How long will the melted down core remnants needs to water to be applied? Can the corium still sustain a nuclear chain reaction if it were exposed?
2 - Whats would occur if water were interrupted at this point? (They called it cold shutdown a year ago but sources seem to conflict)
3 - How long will water need to be applied to the spent fuel ponds? From my understanding the fuel above reactor 4 is somewhat precarious since the building was compromised during the original explosions. Would these fuel rods ignite without water? Is there a real criticality danger if removal does not go exactly as planned? (Wikipedia seems to say criticality in fuel pools is a low-probability event under normal conditions)
4 - Whats your worst case scenario?
Just trying to find some basic scientific answers here, hoping someone can provide insight.
It was your second line actually...
"There are still brilliant mathematicians older than that, but they're not the ones who are doing the most important new work."
Zhang pwned the younglings...
I'm betting most people lose at least eight IQ points by the time they turn 38.
That's why the mathematicians who do the groundbreaking work mostly are younger than 38. There are still brilliant mathematicians older than that, but they're not the ones who are doing the most important new work.
http://en.wikipedia.org/wiki/Yitang_Zhang
Born in 1955 - recently had a breakthrough paper showing that there are infintely many primes with a gap at most 70million
He should have said "Proving that P=NP doesn't necessarily make anything tractable"
Actually in some ways it would be really really exciting and almost certainly a really good thing in the long run, because there are a lot of important, currently-intractable problems that become tractable if P=NP.
Proving that P=NP doesn't make anything tractable, unless you use the ridiculous definition where tractable is the same as polynomial time. What would have practical applications is if someone finds a very fast algorithm for solving all the NP problems. Whether P=NP is not really very much related to the question of whether such an algorithm exists. ML has exponential-time type checking, yet ML compiles don't take that long. Polynomial time is not the same as practical - it fails in both directions.
Factoring is in NP... If P=NP, factoring is in P...
Factoring could be in P anyways as well...
You can't compare symmetric key lengths (based on AES) with RSA modulus sizes. An extra bit in a symetric key gives you alot more security than an extra bit in the RSA key..
Most of the time when you hear that it takes "thousands of years" to factor a prime number
Really? I can factor most primes in my head.. Semiprimes would be a different story...
Sony does publish EQ2 in europe via a company called ProSieben..
Computer, Lieutenant Commander Worf. Confirm auto-destruct sequence, authorization Worf 3-7 Gamma Echo.
Perhaps it needs more structure? e.g. a 10mx10m region shares the same two words and then the third word acts as a reference into that array of 100 points...
CTRL-ALT-F1 to get a non-vga terminal?
I was under the impression Big-O implies the existance of a constant c, for all x > c, f(x) > g(x) where f(x) is the function your bounding it by and g(x) is the function you're trying to describe..
Hence, its just saying "sooner or later", this will always be a bound...
And this is the flaw in your argument. There seems to be some assumption that if it's not under control of Puppet or Chef then it's manual. This is completely untrue. Any competent admin automates their administration. I've been doing it for more than a decade.
Second it's not the host OS and host configuration that makes the servers distinct. It's the data. You can't automate ten years worth of data entry and workflow modules. I suppose it would be unfair of me to hold against you the fact that you don't know anything about my operations, but we're not an internet based company. We're doing stuff other than serving up a bunch of vanity gopro videos. We have several large data centers but we also have hundreds of offices around the world and those offices have their own IT infrastructure. Anyone can stand up a server in 10 minutes in their data center. How long will it take you to stand one up Chengdu given that your primary data centers are in the US and Europe and your network line to the remote facility is 512Kb/s?
The absurdity of the proponents of CFengine, Puppet, Chef, et. al. is that they assume no one has ever solved these problems before. What problems that I have are these products going to solve for me? The emphasis is on "problems that I have". It's not sufficient to tell me what a product does, it's whether it solves my problems.
You are right, there is nothing you can do with puppet that you can't do with SSH, and 10 years ago things like puppet didn't even exist so it makes total sense for you to be in the situation you're in and it wouldn't make alot of sense for you to switch just for the sake of using puppet.
But it's 2013, if you're starting off new - why would you roll your own when many solutions already exist that have been thoroughly tested and extended to have a rich feature set that you probally wouldn't have time to develop as a day-to-day dev op. Furthermore, Puppet allows for this idea of modules that people can write generic versions of "apache" or whatever and often times you don't even have to write configuration systems yourself but instead you can just clone it off github and customize it to your liking..
Your question about standing up servers is silly - why would a more manual solution be impacted differently than a puppet solution based on in-bound bandwidth? Puppet allows for client/server architecture and if bandwidth was your big concern, you could set up a local puppet machine in Chengdu and build servers in that data center based on that...
I worked in a largeish datacenter in 2002 and wrote alot of SSH scripts to manage those servers - it works but its tedious. The benefits of using something like puppet is enormous.. The company I work for now used to employ a full time sysadmin - now the devs just update puppet as we need and it hardly impacts our workloads given how easy it is for us to maintain...
That was a pretty poor review. Giving a summary of the table of contents isn't a review. Additionally it doesn't seem like they recognize that devops and duplicative administration don't fit with a lot of data processing models. There are many organizations that have servers that have a distinct purpose and it doesn't make sense to envision them as just another clone system in "the cloud".
This is why puppet has a very strong inheritance system... We have it broken down as generic server (2 factor/LDAP configs, nagios configs, etc) and then apache_servers which build out the basic web infrastructure and then more specialized configs for one-off speicalized servers... (admin server versus production web servers)
There is pretty much nothing you can do by hand that puppet can't also do - and often it takes just as much time to update a single puppet config file and run the puppet update process as it would be to ssh into the server and make the manual change.
Another advantage is what might go into traditional documentation is now just a puppet configuration.. Oh, fuck, this server crashed? Just roll another in 5 minutes... Who cares about the old one..
1. jQuery core is hardly bloated, its 32k.. If you are willing to drop support for older IE, you can use jQuery 2.0 which is even more streamlined than its ever been.
.on().. Much of the bad javascript I come across is from people who are trying to write it all themselves and have onclick handlers hard coded into tags in a giant unmaintainable mess. Unobtrusive Javascript is for the win and you'll save yourself alot of headache using jQuery to write it.
2. Animations are not part of jQuery, they are part of jQuery UI which is a totally separate library and which I agree, sucks.
3. Native JS syntax for ajax is convoluted..
$.ajax({
url: '/some/url',
success: function(o) {
}
});
Is much more maintainable to me than several lines of new xmlhttprequiest()... blah blah blah... every time you need to make an ajax call...
4. Jquery has lot of powerful stuff that lets you write less code much of the time such as
No kidding. JQuery Mobile is ridiculously slow.
You'd be crazy to use an inefficient and over-weight library like jQuery anyway. Adding jQuery mobile to that is just asking for trouble.
Let's face it: jQuery has long outlived it's utility. It's not even viable for dealing with old browser compatibility issues on the Desktop.
Just learn JavaScript. Your users will thank you. I'll bet that you'll even ultimately save time and effort as you'll spend less time trying to squeeze acceptable performance out of Resig's cludge -- and less time trying to debug the nasty one-liners you're forced to write to get those tiny improvements.
This is dumb for a variety of reasons. jQuery lets you abstract away a ton browser inconsistencies. It also makes you alot more productive b/c you don't have to constantly event wheels...JS by itself is extremely tedious syntax wise . (do you really like document.getElementById riddling your code to the point of unreadability? I'm sure you'd say oh, i'll just write a helper. Well congrats, there you go inventing wheels) Some of the worst code I run across on the web always seems to be the guy that insists on doing things with pure javascript and he has tons of onclick handlers directly on tags and all sorts of other crap which makes sites completely unmaintainable...
I write code for both sides, there's no reason people need to live in their ivory towers...
I've dealt with similiar situations in my professional career. Rackspace's DDOS protection isn't worth it, after 3Mbps, they null routed our box because the size of the attack was so large that it was saturating their uplink capacity...
Prolexic has a cool approach, you proxy your site through them (either web proxy or they can annouce BGP routes for you) and they have massive datacenters that do nothing but scrub packets for you.
The downside is their service is very very expensive ($60k+ a year)
iOS uses the same kernel and core infrastructure as OSX..
2. The current licensing in the kernel makes that impossible
The current licensing by Nvidia makes that impossible... It takes two to tango.
How in the world this was moderated insightful is beyond me - mod parent down, its wrong.
Lots of people don't realize anyone can be a bone marrow donor..
Apparently not me (They don't allow gay people to donate - even if I am HIV-)
If by 250k you mean 80k, then sure..
-rw-r--r-- 1 xxxxx staff 85260 Apr 30 10:28 jquery-1.5.1.min.js
If you're building any sort of complicated website these days, you will use alot of jQuery.. Do you really want to go write a custom ajax handler? why bother..
Plus, using jQuery allows you to leverage tons of other pre-written libraries which were all written on top of jQuery and will avoid alot of cross-browser bugs and repeated code..
echo + html tags is a huge fail...