Yeah, never miss an opportunity to blame the government and the bureaucracy. All that fracking and all that cheap natural gas flooding the market has no bearing on the decision. Most energy experts predicting USA to become a net exporter of petroleum products in the coming years did not affect the decision. 25 billion dollars is a pittance for Duke Energy and the only reason they scuttled the project was because of bureaucracy and regulation and delays.

Expect the same thing to be repeated in West Virginia and South Western Pennsylvania coal belts. They will blame the government, onerous regulations, etc etc and claim "clean coal" was killed by enviro nazis. All the while the natural gas is getting cheaper than even the dirty coal. If you spend more money on cleaning up dirty coal how can you compete with another thing that burns more easily, transports more easily and costs less?

We may disagree whether this boom in fracking and natural gas abundance is a good or bad. But one thing we can be sure is, these entrenched interests would blame the government at every opportunity even when the true cause is thumping its chest like an 800 lb gorilla right on their faces.

You don't understand. Telling the policemen off, calling the FBI jackbooted thugs, firing warning shots at the police under castle doctrine, killing teens in hoodies armed with skittles and ice tea are are the rights Pakistanis would never have in America.

Their no-contract plans are good. Despite a strong smear job by some Attorney General, (probably paid under the table by the big carriers), their phones are not locked once they are paid for. Unlimited talk, text and data, throttle down to 120 kbps after 500 MB, (10 Mbps before). 2GB more for 10$/month/line. 10 more for unlimited. When I got my nexus 4 from Google directly they gave me a micro simcard for free in their kiosk. Another nexus4 I saw from the store did not have as much junk pre loaded. No surprises so far.

My brother was saying that T-mobile benefited immensely in the failed take over big by AT&T. Apparently they had fine print, saying AT&T should give T-Mobile some 3 billion dollars and access to its network, if the deal was stopped by the Feds. So suddenly T-Mobile's coverage area increased tremendously and got some money too. But other are saying that still, T-mobile's coverage is its weak spot.

It is very telling there is no obfuscated FORTRAN coding contests. I think most carefully written lucid code in FORTRAN will beat the winner of this obfuscated c code winner handily.

Cost of using computer or phone includes things other than just money. Speaker's time is valuable too. That is what limiting infinite consumption. But in corporations such things can take a completely surreal turns. There was the apocryphal story about the build group of a major software vendor that was doing daily builds on products (both release and debug, mind you) on branches way after the end of life of products. The product teams had been disbanded but none of them issued "stop build" request and the scripts were faithfully rebuilding a frozen code branch for more than a decade.

How many people laughed at all the rednecks creating weird contraptions to hurl pumpkins down a harvested field in Discovery channel? Now who is laughing, eh? When space travel is commercialized and you are crammed into the economy class seat of the commuter plane to mars, you may have to thank Bill "1 gallon" Schwarzenhammer, winner of Pumkin Chunkin 2021, who was the first one to hurl a pumpkin all the way to Moon, more known for his ability to gulp down 1 gallon of beer without pausing for breath.

It is not your father's fortran buddy! The highly optimized procedures, oops sorry subroutines, are in FORTRAN, But the simulation runs on huge high performance clusters with a mix of GPU, CPU and FPU. You might get a different result if you replace all he 3 meter ethernet cables in the cluster with 10meter cables.

Navier-Stokes equations come under continuum mechanics. Fundamental assumption is even at infinitely small control volumes the field quantities like mass, momentum and pressure are continuous. But we know the fluids are made up of molecules. These quantities are not really continuous when the control volumes are comparable to atomic/molecular dimensions. These molecules undergo random motion induced by temperature (Brownian motion). These are supposed to be the fundamental reason for turbulence. So you can not use N-S to predict the fluid flow far into the future. These things are known even before computers were even invented.

But instead of expecting perfect weather forecast if you are willing to settle for reasonable accurate over reasonable periods of time, yes, it could be done.

Another problem with weather forecasting is communicating the massive data that emerges from these simulations to the masses. Listeners want to know if they have to pack an umbrella. How are you going to tell thousands of users with million different daily routines, whether it would rain long enough when and where they are outside vehicles or buildings to require an umbrella, over a few sentences in radio?

These numerical simulation codes can sometimes do things funny things when you port from one architecture to another. One of the most frustrating debugging session I had was when I ported my code to Linux. One of my tree class's comparison operator evaluates the key and compares the calculated key with the value stored in the instance. It was crapping out in Linux and not in Windows. I eventually discovered Linux was using 80 bit registers for floating point computation but the stored value in the instance was truncated to 64 bits.

Basically they should be happy their code ported to two different architectures and ran all the way. Expecting same results for processes behaving choatically is asking for too much.

Almost all the CFD (Computational Fluid Mechanics) simulations us time marching of Navier-Stokes equations. Despite being very non linear and very hard, one great thing about them is they naturally parallelize very well. The partition the solution domain into many subdomains and distribute the finite volume mesh associated with each sub domain to a different node. Each mesh is also parallelized using GPU. At the end of the day these threads complete execution at slightly different times and post updates asynchronously. So even if you use the same OS and the same basic cluster, if you run it twice you get two different results if you run it far enough, like 10 days. I am totally not surprised if you change OS or architecture or big-endian-small-endian things or the math processor or the GPU brands the solutions differ a lot when you make 10 day forecast.

Google will merge the self driving car technology it has developed with some robots from ai.mit.edu and complete the mail delivery from the cluster boxes to the door. But first it has to complete the robot that will open the mail and merge it with the OCR technology it developed for the Gutenberg project.

Just do an yum update lib.somedamnthing

The smart phones are getting smarter by leaps and bounds, dedicated gps systems with life time map updates are just 100$. The nav package has some minor advantages like muting the car audio, pausing the music, and some easier reach controls. But they nickel and dime you for map updates, and they are way over priced. You are better off not getting them.

Are the malicious apps being distributed from the playstore? Or from other app store?

Whats with people acting as though everyone and their grandma should do it in their personal computer for some new technology to be a phenomenal breakthrough? Does your grandma compute page rank of billions of pages of the net in her home computer?