If you're that severely bottle-necked by a 4+ GHz quad core then this is not a typical DX11 game.
We already know this isn't a typical DX11 game. They're using way more draw calls than a typical DX11 game simply because DX12 allows them to make more. That's even stated in the article.
The Developer now must know MORE about the underlying hardware to make the best use of Direct X 12?
Uh, yeah, that's what a lower level API means.
Not unless they're faster than you. Which they're not.
There are plenty of older fighter jets that are noticeably faster than the F-35.
Especially when the rules of engagement require visual confirmation before weapons release.
and the F-35's stealth capabilities pretty much ensure it's going to get the first shot at BVR.
You completely ignored the fact that rules of engagement don't currently permit firing BVR.
So, a few issues here and there, but really, why not?
The amount of effort required. Not only does Google have to rewrite the relevant portions of Android to use C#, all the apps in the store need to be ported too.
There are lots of good alternatives to preprocessors that achieve the same goals without many of the drawbacks. The first one I think of is lambda expressions.
Ironically lambda expressions are essentially little more than just syntactic sugar (ie, preprocessor) implementations of functor objects in C++.
irreversibly destroyed Java's fundamental value proposition as a potential mobile device operating system
Well there's the problem. Oracle thinks the language and runtime are a complete operating system. There's nothing stopping Oracle making a different OS that uses Java. In fact, the vast amount of libraries for Android out there should be easy to port. Next we'll hear how Microsoft destroyed the value of C as used to build an OS.
"You can't get very far in this world without your dossier being there first." -- Arthur Miller