Rhenium, also used in turbine blades, goes for about $2500/kg... so, $1/gram for hafnium doesn't seem like much at all.

Seems like those are applications that scream, "CHEAPER TO DO WITH DRONES!" to me. :)

It's interesting as the unique tail section was actually touted as a "safety feature" by the company. I'm not necessarily saying it can't be the case, but like any feature, even a safety feature (see: exploding airbags), defects or improper use can cause more harm than in it's absence.

An improperly implemented safety feature (emergency ballast blow system) contributed to the loss of USS Thresher... In the same way, the Apollo 1 crew died (in part) because of a system (a well locked down hatch) that had been installed to prevent a repeat of an earlier accident. (Which, by morbid coincidence, one of the crew had been involved in.)
 

It's a bit strange, as it seems like such a fundamental error - not some obscure feature that could be overlooked. What pilot would say to himself "Hey, I know I'm supposed to unlock the tail at time X, but what the hell, why not just do it now?" It seems really strange that they wouldn't have precise procedures for this, since it's such a critical part of the entire design.

It's not so much that, as the pilot appears to have become confused due to a) the simulator not properly conditioning them, b) lack of recent and overall experience with the vehicle, and c) high cockpit workload at that point in the flight compounding a) and b). At least that's how I read the report. (The abstract and summary of which is not clearly linked of the summary or TFA but which can be found here.)

From my experience in the Navy, I can say that obtaining those reflexes isn't easy, and neither is maintaining them (regardless of experience).

Think of the countless small ways in which knowing some code, or scripting has been useful over your life - sorting simple lists, renaming things in batch, formulas in a spreadsheet... etc. etc.

Even if most people will not be doing code professionally, it will help them do little things for themselves. It will also help them understand to some extent why software driven things behave the way they do, and even to make more informed choices as to software driven hardware they buy (and that is the future).

It's not like a flood of really bad programmers will get through most hiring barricades, already famously difficult to storm. They will go on to do things besides programming, where light programming can help them.

If there was a criteria for safe unlocking of the hinged tail section then why wasn't it interlocked until the criteria was satisfied?

There are problems with interlocks that aren't often appreciated by the armchair engineer. They add weight and complexity to a system. They themselves can fail. They add to the maintenance burden. They add to training, Etc... etc... TANSTAAFL.
 

A bigger error here is reliance on operator training. It's the least reliable form of ensuring a certain outcome.

Yet, for being the least reliable, it's a method that works very well - presuming the operator is properly trained.

It's not all that hard to stick with a toolkit version for a couple of months (or to be honest, even a project lasting up to 18 months is no big deal.

That depends on the system. If you are doing iOS development, while 18 months is possible it's not advisable due to every new version of XCode (one major, a few minor updates every year) having more advanced tooling, compilers, frameworks... furthermore you are going to have to use a beta version at some point to test and debug your software on for un-released versions of iOS that you have to make sure you work well on before they are released.

I see your point, I was more speaking to the attitude of people that want to spend years without upgrading the underlying technologies involved in building and running your project... the longer you wait the worse the transition is, and like I said in the meantime you are also missing out on things that could have made development easier or resolved bugs you had to fix.

One can only hope that things will get better.

The lack of NFC is disappointing.

If you're not planning to use your cell phone also as a Credit Card...then what other uses really are for NFC?

I'd not want any of my CC info on a phone that can be stolen and cracked into. And from the article, apparently not that many people out there are even using NFC functionality, so I'm guessing to many it is no great loss.

What all do you use NFC for so much that it is a deal breaker for you? Seriously curious.

Thanks!

On the other hand if you fall behind current dev tools, you miss out on the potential for a lot of community support, risk being crippled by the bugs that remain in the older system that are fixed the new, and hamstring your ability to work as effectively as you might because you cannot use newer tooling/frameworks to help with development...

Yes SE has a lot of stuff changing, it always has and always will. But cringing from the pain will not help, SE is not finding any kind of safe plateau (because there are none). It is moving ever forward at a reasonable pace, using nettles as handholds where you must grasp them firmly as you ascend, living with the brief pain to move forward.

FPGA can also have backdoors.

I don't have any problem with the account verification though - it's just a variant of the 2-factor authentication so don't complain too much, it may prevent you from getting your account hijacked.

Well, I just would rather not give Google my cell phone number...

Sigh... Coal is only useful for base load. The spool up time for coal is too slow for peaking.
Natural gas is ideal for peaking since you can use it in gas turbine plants for peaking since the spool up time is so fast.
I showed you references do you have any data at all to back up what you are saying?
France may or may not use natural gas for base load but many nations do since it is so cheap and clean.
I would say that the engineers in France are knowledgeable and I would also bet that they would agree with what I am saying. Too bad it is the political parties that want to cut nuclear.

Does this finally mean I'll be able to post replies to my own YouTube channel and other's videos?

I have my account, that predates Google taking YouTube over. I've resisted all these years going to G+ or giving them more information....but for that, Ihad to give up being able to post comments and replies not only to other peoples' videos, but even to my own.

This will be a welcome change if that works!!

Now, if they'd also do away with trying to occasionally "verify" your account with a phone call. I fear I"m gonna have to go get a disposable phone for that one day...but hey at least this is one step in the right direction.

My Western Electric Model 1500 begs to differ.