The UI is slick, but why should I trust this black box?
The "how does it work" section doesn't even mention
* modeling assumptions
* training data (if any)
* validation (if any)
Why is this better than, say, giving the 25-75% range around my "best guess" assuming log-normal duration and the variance of prior project completion times? Can you demonstrate that it's better than that?
It's not better; it's almost exactly that, as detailed in many comments below. I choose slightly different thresholds -- 75% is not very high, you'll be wrong one time in 4 -- but that's the approach.
If you're already doing log normal modeling of your estimates, and including sick days, social loafing, etc, then you don't need Vistimo Quotes. Just keep doing what you're doing!
This is something I would buy if I had confidence in the simulator.
Why not write a blog or a brief white paper giving some hint of what's going on behind the scenes?
Generally speaking, every bit of energy someone spends being cool (good UI) comes at the expense of energy spent being good. Maybe you've done some serious work on the simulator, but I can't tell from your marketing material.
How do you distinguish a nonsense model from a good model when you don't have a writeup, you don't have validation data, and it is not possible to run cheap experiments?
I'm not saying you can't make money selling an RNG with a slick UI, you certainly can.
This article contains no new information, and could be accurately summarized "guy whose boss spent $1 trillion on the F-35 says the F-35 is a good idea."
He also calls it a supersonic fighter, which isn't true. The coatings cannot withstand sustained periods of supersonic flight.
And also, the author is an operator, but not necessarily someone involved in the engineering or acquisition.
Nonetheless (and I say this as someone who was severely soured by my involvement with the program), people get tribal as to whether the JSF (provides an unmatched capability) XOR (is the zenith of acquisition malpractice). It's not either/or; both are simultaneously true.
No one in DoD R&D/acquisition fails to appreciate how expensive these things are and this realization is certainly driving long-term decision-making.
"Just imagine how the F-16 program would have been covered today when they were crashing an aircraft almost every two weeks during several years in the ’80s and ’90s (the F-35, by comparison, has only crashed 3 times in over a decade of flying)."
I had no idea that an F-16 crashed roughly every two weeks while being debugged. I imagine I'm not the only one.
Most supersonic fighters can only do so for very short amounts of time. The F-22 is the only operational fighter with real sustained supersonic capabilities.
That is false. Maybe you mean "only operational US fighter".
The difference between the F-18 and the F-35 is that while the F-18 might need extended maintenance after prolonged (read : more than a minute) supersonic flight, the F-35 may suffer catastrophic coating degradation that may be fatal in the same flight.
As for other operational fighters, the Dassault Rafale can supercruise indefinitely the Gripen indefinitely at Mach 1.3, the Eurofighter indefinitely at Mach 1.8, the Sukhoi-35 can if outfitted with the AL-41F-1S (meaning, some operational Su-35s can supercruise indefinitely, but not all). The F-22 is far from the only one.
That is incorrect. They can all supercruise with an air-superiority loadout except possibly for the Gripen where we are not certain, for over 20 minutes.
"Supercruising" means flying supersonically for at least 20 minutes. In a fighter aircraft the salient requirement is often not the time that the plane can fly supersonically but the distance. The Mig-31 has a combat radius of 450 miles at Mach-2.35 and a top speed of Mach-2.85.
If you need a fighter to fly 500 km and engage a target, why wait 25 minutes for a super-cruising mach-1 fighter when a Mach-2.3 craft without super cruise can get there in 10 minutes?
That's absolutely true, and it definitely matters when you're designing something that will see productive use for the benefit of the people paying for it, but it's not obvious that that's the case here.
Not really. The main limiter for supercruise in the F-35 is sub-par stealth coatings that unlike the F-22's cannot handle the heat. Otherwise it could supercruise, maybe with some engine tweaks.
You can see it that way. It's really more politics than cost in this case though.
From an engineering perspective local political optimization of a national project is what I would call ineptitude. But you can call it by another name.
That's a little disingenuous. For other platforms, the constraint is fuel. Afterburner guzzles fuel. Only F-35 requires expensive and protracted maintenance after supersonic flight.
Which is another area where F-35 is lacking: range. Without external fuel tanks it can't fight in the Pacific.
You do, but the closer they get to the target the greater the likelihood they have of getting sunk. The likelihood approaches 100% as the distance to the target is reduced.
Not necessarily, the US has land bases in the pacific.
If you're going to base your availability of air power, which is the main determinant of success given the American military doctrine, on having a secure and available carrier at all times, you may be putting yourself in a bind when anti-ship weapons start proliferating and you become forced to increase distance between those defenses and your carriers.
My point is that if there's a war with China then the US will seek to contain it to the East China Sea. Kadena is 700km to the Chinese mainland, which is well within the F-35's combat range of 1000km.
The issue with Kadena is that it now become too close to the Chinese mainland, enough that it could be disabled by missile strikes.
The best thing that could be done would be to have enough range to be able to fly out from a carrier that's relatively safe from antiship missiles. But that may well become impossible anyways as antiship missile evolve.
The "how does it work" section doesn't even mention
* modeling assumptions
* training data (if any)
* validation (if any)
Why is this better than, say, giving the 25-75% range around my "best guess" assuming log-normal duration and the variance of prior project completion times? Can you demonstrate that it's better than that?