The Economist has a Christmas edition to do, which includes extra materiel which is "interesting" but not current news, to compensate for not producing an edition next week. Even if you got it in marketing 101, not everybody dis, and the Star Wars release makes it topical.
Nobody buys a Porsche roadster to carry groceries and kids. That is a different market, which Porsche as a brand will never enter, electrically or fossil powered. They do make SUV type vehicles, but even so, their buyers are not thinking kids and groceries.
The problem is that the Cavendish is sterile and only reproduces from cuttings. The seeds, those little dots inside, do not develop at all. So every Cavendish banana plant in the world is, in one sense, the same plant: genetically identical and cannot be bred from.
So you have to go back to another variety and breed in any of the qualities of virus resistance, productivity, size, flavour, edibility etc. which it does not currently have. Which is not impossible, but no such varieties have been produced in the last thirty years or so, so an estimate of decades dies not strike me as unreasonable.
I imagine there has been such an investigation. But first, you have to decide what was "the decision" that caused the accident. In aviation they say that an incident is none things going wrong at once, an accident is ten. If five people each believe that one of the other four had put the safety locks in place, and none had, which of the five made the decision which caused the accident?
The company was certainly liable, and has been fined. The question is, was any person liable, to the extent that the could be imprisoned for manslaughter?
The problem being, apparently, that nobody made "the decision". Due to lack of communication, one crew thought that status was A, and the other that it was B. Should you sent to prison the person who allowed live power in an area he thought there was nobody working, or the person who sent people to work where he thought the power was off? Or the bosses in the two different companies involved? Or the bosses in the employing company, a bank, the only place the chains of command met, who though they were employing competent contractors? The problem is that the structures were so confused that, though they didn't realise it, there was no-one in control. Finding someone guilty "beyond reasonable doubt" is almost certainly impossible.
But to know to turn it off, you have to know it is on. And that appears to be the problem here - people didn't know what was on.
Reading the article, it appears that it is not that "somebody made the call", it is that communications between the teams working on the project, from two companies, was so bad that one crew didn't realist that people would be working in the area, and the other crew didn't realise it was live. Incompetence, not risk-taking.
No, to eliminate most healthcare, you have to eliminate ageing. Cancer is not a hunger related disease, nor is Alzheimers. Only somewhat cardiac. It is alleged that 50% of health spending is in the last six months of life. Hunger is a major problem, and hunger has health consequences. But it is not the major driver for healthcare demand.
Nonetheless, you need to get file access to such devices to read the passwords. The trick here was that they managed to get the kettle to, effectively, spit out the WiFi password. Until you compromise the network, lots of things may have lots of files inside them, but without physical access you can do nothing. This allowed them to compromise the network without physical access.
The armed forces have been spending big bucks on researching this sort of thing for a long time. They, too, do not actually want to kill people, especially when it is some brainwashed kid sent out on a suicide mission. While obviously prepared to kill, their ideal is a complete victory with no casualties on either side. So they have spent a lot of money on researching pain rays, stopping foams etc.Unfortunately with essentially no success. It seems that anything capable of stopping somebody armed and ill-intentioned has a high probability of killing them.
Which make sense. The human body is not a single co-ordinated machines, but a number of semi-autonomous subsystems working on a team job - of making the body of which they form part a success in the world.
Many display systems are. It sounds like a heap problem to me. If you are building a display which only selects and monitors an underlying database, which may well be managed in C, it is plausible to use a higher level language, But C can have heap leaks, too.
The loose description sound like something not being garbage collected when it should have been. So no single change cause the problem. It might well have been caused by controllers playing with a new toy, in a way they would never do once it had settled in and testers would not do, It is difficult to observe heap leakage - even if you check free space after a run, it is not clear what the right value is.
Nothing ever becomes real until it is experienced. - John Keats
