It's a ruse by Salmond. He is goading the UK into saying "no" to a shared currency so that Scotland can't, by law, pick up a share of the national debt.
Instead what is likely to happen is that Sterling will be split into two: A British Pound and a Scottish Pound. Scotland will get its share of the Bank of England assets and the rest of the UK will get its share. Similarly the debt will be split so that Scotland takes their share of the debt and rest of UK takes its share. Currently the UK government is saying that it will back up all the debt to prevent the threat of independence causing a down rating of debt. It's highly likely that if independence goes ahead then they'll back track on that saying that the situation has changed and that borrowers will have their debt split between the two new nations. That or if Scotland say they don't want any of the debt then they won't get any of the assets either.
Unfortunately the scam works the same way with advertisers as with viewers:
"So you want to show your advert on ESPN. Well I'm afraid we only sell that prime time ad slot in a bundle with ad slots on all these other channels."
And so the merry-go-round continues to spin.
You can't get the full text of a copyrighted work from google, no matter how hard you try.
You may not be able to get the full text of the copyrighted work, but Google can and has. Google are profiting from an unauthorised copy made of a copyrighted work. If google are allowed to do it, why can't I? I only want to make one copy of each book from the library. I don't intended to sell that unauthorised copy to anyone, heck I don't even intend to let anyone else see even snippets of it. What's the difference? Why are Google allowed to make copies for their own purposes but I am not? Is it because they are a rich company who can afford lawyers to override copyright laws?
Personally, I believe copyright terms are far too long, but if you're going to have them then you should respect them in all cases. It can't be one law for the rich and one law for everyone else. If the term of copyright is too long and causes all these problems with orphaned works, or works being lost to the public domain because there are no copies left when the copyright term expires, then the problem is with the copyright term and we shouldn't allow exceptions for rich companies to circumvent the problems with the law.
Also at EU 20-28k, you can pay for decades of electricity usage, and that's not even taking into account maintenance. Waste of money.
Decades only at current prices. Prices having been increasing significantly over the last few years and that trend does not seem likely to change any time soon. If for EUR 20K you can lock in your energy prices for the life of the system (also measured in decades), then you are very likely to make significant savings over that time.
For example, according to UK Department of Energy and Climate Change figures, electricity prices have risen by 63% since 2005, and by over 250% since 1987 (considering 25 years being the typical life of a solar PV installation).
Except that no-one is going to replace a perfectly good vehicle with an autonomous one unless there is a benefit to them. It will be that pepole just move to an autonomous one next time they replace their vehicle. More likely the trend will actually be more and more automation in "normal" vehicles each generation so that everntually the majority of vehicles are autonomous (or capable of being autonomous).
Alongside that will the people who actually see an economic benefit from an autonomous vehicle. If it means that they can spend more time with their family or doing things that are more productive during their commute/travel then they'll buy an autonomous vehicle.
So it's not just the saving from the purported reduction in accidents that makes the economic case for autonomous vehicles, it's the whole equation
The autonomous car would be able to quickly decide whether coming to halt in its current lane is safer or if manoeuvering into other spaces to avoid the child/dog is safer - and probably much more easerly than a human driver who can freeze in panic at an unexpected situation. Additionally the computer can potentially make the cold hearted decision that breaking but still hitting the obstacle, because there is not enough stopping distance, is ultimately the least bad thing to do - for example if there is heavy traffic in the on-coming lane and pedestrians besides the road.
It could also, for example, automatically sound the horn to alert people and perhaps enable the child/dog to notice and get out of the way. A human on the other hand is more likely to be still be evaluating the situation and reacting by slamming on the breaks and not have the foresight (or the co-ordination) to do this.
When considering whether someone thinks they are better than average in driving skill you should look at this study
Svenson (1981) surveyed 161 students in Sweden and the United States, asking them to compare their driving safety and skill to the other people in the experiment. For driving skill, 93% of the US sample and 69% of the Swedish sample put themselves in the top 50% (above the median). For safety, 88% of the US group and 77% of the Swedish sample put themselves in the top 50%.
You seem to have ignored the problem of generating the millions of natural language questions that would then require natural language processing to solve. It's easy to come up with one or two as a human, like the George Washington question above, but unless the majority of questions posed as a replacement for CAPTCHA are unique then all that will happen is that the spammers will use a human to solve the relatively few questions and store the result in a lookup table.
We can see how difficult it is for spam bots to generate to natural language posts so why do you think it would be easy for a computer to generate meaningful natural language questions?
So to paraphrase you: now every web site would need a Watson-class supercomputer to stay in business, being a site operator suddenly doesn't seem very lucrative anymore...
Errm, that's exactly what waterfall is. You have a big upfront specification phase (essentially your user manual from your example) followed by a design phase followed by development etc.
The problem is that users truly don't know exactly what they need, and even if they did, those requirements will change over time in response to the market changing. So by the time that you've spent months writing a spec, 50% of what you specified will not be what is actually required. Worse you've now spent months writing out of date documentation and have NO software to show for it and opportunity to start getting back any of your investment - paper specifications are not a business asset. Then you spend still more months writing code against that spec, meanwhile another 50% of the remaining correct spec is now out of date meaning that by the end of development you've actually only delivered 25% of what the customer really wants and 75% of what you've developed is wrong. And you've still not got any software into production to be returning on the investment you've made.
That's why people looked at other ways of developing software and why agile gained traction.
It's not a perfect approach, but IMHO it's the least bad approach that we've tried so far.