You're assuming said fusion plants would be radically cheaper to construct and operate than existing fission plants...something the anti-nuclear activists would probably complicate despite the obvious benefits of fusion over fission. Never underestimate the public fear of the word "nuclear" even if the processes involved are ridiculously different.

I can hear the rallying cry now: "They want to build a plant that works the same way as a thermonuclear bomb! Do you want a nuclear bomb IN YOUR BACKYARD???"

People are still terrified of fluoride in their water. Can you imagine their reponse to the above?

Fusion power is roughly 20 years away from being viable...and has been for the last 40 years LOL.

Seriously, I'll start worrying about proliferation risks when a commercially viable fusion reactor DESIGN is created. Building one -- assuming it's ever viable to begin with -- would take years, which is plenty of time to address proliferation concerns before it came online.

Becaused they asked me to CC them on such issues, and I don't feel like keeping a log of when everyone was gone and what happened that they might care about, so I can resend it when they get back. If it is something I care about I will talk to them when they get back. If it is something that they care about and know about then they can ask me. The problem is the stuff that they care about but don't know to ask about. Skimming an inbox full of CCs works well for that.

Absolutely. There are many advantages to this approach:
* Users can get info they need more quickly as they are already in the correct context to get help on that feature, and don't have to search a document.
* Users are more likely to use integrated help than a huge user manual, saving you support time.
* It is easier to enforce a policy of updating documentation when you update code.

The only thing your separate documentation needs to cover are high-level concepts of the application, and common HOWTOs. If you must have a monolithic reference document, then use a system like docbook that generates HTML and PDF, and integrate HTML help into your application.

Of course this is assuming that these are GUI apps. Server apps or anything that needs configuration outside of a GUI must have full reference documentation.

To put this in perspective, 5,000 sq. mi. is a square about 71 miles on a side. Compare this to the total area of the Gulf (615,000 sq. mi) and you'll see this "dead zone" occupies just 0.8% of the Gulf. Is this something that needs addressing? Absolutely. But it's not some horrific cauldron of death like the headline tries to make it out to be.

It was a bit more than that. He recruited Obokata to RIKEN, was her mentor, and supervised her STAP work. As you said, there is not even the slightest hint that he was engaged in any misconduct, but the RIKEN investigation did find that Sasai and Wakayama carried “heavy responsibility” for what happened, and the incident opened questions about how closely co-authors and research advisers should oversee the work of their underlings.

The scientific model is quite simply:
1) Develop testable hypothesis (aka theory)
2) Develop experiments/observations to test hypothesis
3) Perform experiment/observations
4) Repeat
Anyone who participates in any of these steps is performing science. It took a while to find practical tests of String theory given it's extreme generality, but several have been suggested and a few have even been performed, ranging from the scale of planetary motion to LHC data.

No, nothing in this article says anything about the site selection which is still pending, just that it will be a joint venture between Tesla and Panasonic rather than Tesla going alone as was previously believed.

The quickest numbers I could find say that at the scales of large power-plants, the generator is very efficient, but the turbine not so much, around 50%. This would put the system as a whole at around 40% efficency sunlight -> electricity. That's competitive with the best solar voltaic systems tested in the lab, and 50-100% better than practical systems on the market. Assuming their system really does scale up to power plant sizes, of course.

Bat Dad

And no matter how much evidence the US or Ukrainian government produces, no matter how detailed and annotated, Russia will dismiss it with a wave of a hand as fabricated, slanted, biased...whatever they want. They'll never admit responsibility.

Yes, because UN peacekeepers have such a long, sterling reputation on stopping stuff like this from happening.

But regardless, the UN will never do anything in this conflict. Russia holds a veto in the Security Council, and they will stop any such measures from ever happening.

Microsoft brought over 25,000 Nokia employees in the merger of which 12,500 are to be laid off in the next 6 months. Probably all that's left is the hardware engineers, with nearly all of software, marketing and management getting the boot.