It appears you are missing the point I am trying to make. The current technology will not get us very far, I am unfortunately very aware of this. Also the best chance, under our current understanding of the universe is the Alcubierre drive and that would use up something along the lines converting Jupiter's mass to energy.

To get back to my analogy, we two are living in the bronze age. I say traveling the sea will be the future and you say that on our current technology (canoes) we will never be able to cross the ocean.

There is no reason why we can not get a closed loop system to sustain itself. Also there are potential improvements in current rocket technology or rather propellant. Sure we will probably not leave our solar system withing this millennia, but there is no reason why we can not go out into our solar system.

Finally, if you take Project Orion, technology from the 1950s, you get a trip time of 133 years to Alpha Centauri. Although it exceeds a lifetime of a human, it is not completely outside of your reach. It has a few other issues, such the radiation and life support for such a trip, but it is not fully outside of the reach of what we can do.

The "harmless" was in relation of the effort and care needed to take case of failures. I know of no food production lines that can not be put in emergency stop. The same is with medical, at most they operate a batch process and in the worst case they need to inject a stopping agent and loose one reactor. The difference with chemical plants or power plants is that there is no "emergency stop". You need to continue operation in the case of a fault and try to slowly get it to a safe state. The alternative is basically "BOOM".

No offence taken. It was very condensed and had

Funny that our software is used to engineer and operate FDA approved production lines. Food & Beverage and Medical are harmless in comparison to continuous Chemical. If a contentious chemical plant fails, you don't just have loss of production, you may need to scrap part of the installation. With some processes the reaction happens in the piping and the material may harden in the pipe requiring the replacement of said piping. Not to mention the operation and control of nuclear reactors.

But since we build the engineering and run-time software for industrial installations, we are decoupled from their narrow and seldom maintenance windows. Nevertheless there is little margin for error. I would rather have a body of software that is properly maintained than a collection of band aid. (Some bits actually are in that state.) To counter that we normally have a ratio of 1-1 developers to testers and in cases of major versions 1-2. Just because I gloss over the budget allocations of new development (80%) vs. maintenance (20%) does not mean we are not committed to quality. Rather the opposite, cleaning up code so a feature fits better in the total architecture is right thing (tm) to do than to try to wedge a the square into a round hole.

But my point stands "we don't have the budget for maintenance" is a lame excuse. Either the maintenance is important and it will be done or it is not and then the developer needs to get his priorities adjusted with the business requirements. Actually "we don't have budget for X" within company that make billions of revenue always a lame excuse. If it is important it will be done, regardless of budget allocation; if not... well then it is not important.

No that version is stated for beginning of 2016 and I am not working for Microsoft.

I think you sort of misunderstood what I meant. My name is Sean Farrell and that should almost tell you everything you need to know. I am US-American and German by Nationality and currently living in Germany. Looking at the British isles, culturally England, Scotland, Wales and Ireland are quite similar; at least in contrast to the rest of Europe. If you take an Irish, Scottish, Wales and English person and put it in front of, say a French and ask him where they are from, he would have serious problems answering correctly.

The point I was trying to make was that, in response to GP, yes from the outside they (Scotland / Ireland respectively) seem quite similar with England, but if you ever mention that in a Pub you probably will wake up ER.

On the other hand Northern Ireland / Protestant, the situation is different; most will claim some form of English or loose affiliation with England. This being, because they factually are (decedents of) immigrants form England. But then again, who really is "Irish", the Celts who originally settled there, the Viking who came later, the English immigrants that came later.

The Royal Bank of Scotland is not Scottish? It is not clear who owns it, since it is publicly traded; but I don't think they would close down their HQ in Edinburgh, just because Scotland is now an independent country.

I honestly think the EU would be fully willing to integrate Scotland from day one. Some eastern European countries will probably complain, but that is just political blocking going on. I am pretty sure that they can turn something like Scotland can "inherit" their EU membership from the UK. (That is under the assumption that the Scottish government actually wants to.) Following that the EU would probably not mind adding Scotland to the Monetary Union and thus give them the EURO. More volume is basically always better for a currency.

In addition Norway is not in the EU and they seem to do well too... I don't get what the doom and gloom is. I understand both sides politically and emotionally, but I doubt that an independent Scotland will not be the end of the world everybody is painting.

You could say the same thing about Ireland. I think the Irish would disagree though.

Did you actually read the GP post I was jokingly replying to?

Well at least some mods got the joke...

No it compares to: You told(1) me to inflate the front left tire, but the tire was worn and had a hole, so I needed to change the two front tires. You should also consider changing the back tires and the brake pads look worn, but it's your car.

(1) "I don't care how, make it work!"

I am a lead developer and bill against two accounts when developing (a third account when I tell people what they should do). I resolve the issue by simply looking at why I started working on something. Did I start working because bug or performance issue forced me to improve the bit (maintenance) or did I start adapting a piece of code because of a feature request (new development). By keeping the "boy scout mentality" (leave the code in better shape than you found it) my peers and I are able to keep a body of software running that was originally written in 1993. Just because you are slightly bending accounting nitpicking does not mean you go gung ho hacking though the code. By the way we are going to release V8.1 next month.

Except that "new development" and "maintenance" are just labels. As long as there are no new user visible features (apart from improved speed and smaller memory footprint) all development is "maintenance". I understand the rationale between the maintenance / new development budgeting and can totally work within it's framework. But sometimes you just need to clean up code before you can add this new feature (100% "new development") and sometimes you need to replace a legacy database system with a modern one to keep the application running smoothly (100% maintenance). You try to answer the question "why am I doing this?".

The "you can't do that because we don't have the budget for maintenance" is just a lame excuse for two situations, either you just don't have the budget to do it or your manager is scared that you will break something. In all cases it is just a failure to communicate properly, which is especially lame when prefixed with "I would like to let you do this, but..."

I think Bruce Schneier put it quite blunt "trust the math". There is a relative high degree of certainty that the math is solid. You may need to use different "magic numbers" then the specs, but apart from that the math should be solid.

The problem actually comes in the implementation and security protocol. Implementation of the crypto may be faulty. The key may could be intercepted when you are sharing it with the other party. The system the key is stored on is vulnerable to attack. Systems processing the data need to decrypt at least bits of the data to process it and the clear text leaks. The implementation is vulnerable to side channel attacks.

As Tuidjy puts it, everybody with a solid CS background can implement a crypto scheme. That person (having a solid CS background) should also know that it is technically impossible to build a 100% save scheme. You only shift the goal posts by using crypto. The best you can get is to the point where they need to install a camera that reads your screen.

Semantics, but... the data "itself" does not generate revenue; it is an auxiliary to the expensive device. Contrast that to Google, the data is the central bit about the targeted adverting. That is the distinction done here.

That is better because?

You are missing the point that the amount of money invested into R&D actually means something. As it stands I have the impression that each dollar spent by SpaceX in R&D has about the 10x impact then Boeing's R&D. SpaceX is extremely lean and have quite something to show for it. The problem with Boeing's R&D is that most of it is classified in some military contracts and as such hard to evaluate from the outside.