...that people would stop calling it copyright "reform". It makes it sound as though it's broken, and this will fix it, making it all rainbow and sunshine.
I'd agree on the first part, but not the second.
Apple's iPads are so incredibly cheap to make that no one seems able to match the price on them.
So what is your expertise on pricing on tablets?
Sorry but you are an ungrateful ass or something. There were only 4 paragraphs in the post. Get over yourself.
It takes more energy to send something into the sun than to send it further out into the solar system.
Probably because Chrome is webkit underneath it all, and that contains Apple's standard web dev debugging tools.
Google put a nice UI on it, as well as doing good work in sandboxing it. I'm not sure if it's more reliable, but I've been finding Safari reasonably flakey.
It's what they are doing right now - pumping sea water onto/into the cooling ponds.
I was really imagining the spent fuel rod pool in the same building, just down a long way. That way you could still use the same crane mechanism to move it (presumably a gantry crane), but you would just need a lot more cable.
Issues of accurately aligning the longer pendulum into the pool are left as an exercise to for the designer.
If they cooling ponds were slightly below sea level it wouldn't have been a problem either.
A pipe leading from the sea that could be opened in the case of loss of power, or alternatively that is always kept closed by power (so it automatically opens on power failure) would have been a better design.
iOS has many features for blind people - apparently it's one of the best machines out there to use.
I argue that testing, process, management and analysis all require statistics. In practice this is done using continuous functions even when the probability distribution is discrete (e.g. the central limit theorem.)
I agree with you there. I had thought about stats, but hadn't considered the continuous functions aspect.
Implementation requires knowledge of first-order logic, which is mathematics.
I'd be surprised if this is the case. Can you give an example that shows why it is necessary?
Design and requirements-gathering require knowledge of the problem domain, which I hope will involve algorithmics and mathematics. If they truly don't, I feel deeply sorry for any developer working on the project.
I'm all for discrete maths, which most algorithms are (graph searching etc). I think that continuous maths (with the exception above) are limited in their usefulness for most domains.
The software engineering part doesn't need (continuous) math.
Testing, process, management, analysis, design, coding, requirements gathering are all fairly math free.
Sure there are some domains that require continuous math, but there are a hell of a lot of other domains that don't.
...did he say if you should wear a condom while using the internet?
People want to know!!!
He's apparently a pain to work with, is extremely demanding, but he's forced the company to make brilliant products.
I like your well considered sentiment. It is quality, and will last me a long time. May I buy it?
"They've done a great job at getting us to work at getting rid of all our Solaris systems as fast as we can."
That's ok, you can always switch to Mac OS X and XServes... oh, wait....
It is easier to write an incorrect program than understand a correct one.
