We are thrilled to have them. We would much rather contend with growth problems than a loss of tax revenues, reduced property values, list employment, or low quality jobs. We have subsidize part of their expansion, but the growth will pay back that investment in 5-7 years. We can live that ROI.
EDIT: cleanup/clarification
That's the point.
It's the shitstorms that generate the tweetstorms that impact their larger bottom line.
We can glimpse a world-wide stack-ranking system: "Echelon [0], who are the 1000 individuals most threatening to our strategic position and what will be their whereabouts today?". "Matrix [1], please dispose of these individuals at these locations". Let's pray there will still be some humans between step 0 and step 1. Worse, by the logic of MAD, it is possible we are going to end up with 2 such systems, one for USA and one for China, caught in a new cold war. Think distributed Vietnam.
[1]: https://www.intelligence.gov/ [2]: https://www.fedscoop.com/cia-confirms-multi-cloud-procuremen...
Also, Amazon has a tremendous footprint here already. Their largest region is located in Ashburn (~25 miles east), CIA is roughly 5 miles for Crystal City, Herndon and Ballston have large AWS sales/engineering offices, and Richmond (roughly 1.5 hours south) hosts one of their largest distribution centers on the east coast. In short, they were committed to this area long before HQ2, let alone JEDI. They cannot be happy about losing the contract award, but it was only one of many things Amazon/AWS are going in NoVA.
And 10 billion over 10 years is what? Maybe 3 to 5% of Amazon's yearly revenue? You really want to be at the epicenter of the shitstorm that will happen if the project goes over budget and you still haven't delivered anything anyone in the DoD actually uses? (Maybe I shouldn't have said "if the project goes over" but "when"?) Especially being a big tech firm nowadays?
And you're gonna step into all that unnecessary drama for access to a 10 year / 10 billion project?
I don't think so. Not for a billion a year in revenue when you're already sitting at over 230 billion a year in revenue. (Or even just the over 30 billion a year that AWS alone is sitting at.)
Admit it man, politics being what they are these days, particularly for big tech firms, it's just not worth it.
First, Oracle has completely open sourced the JDK, for the first time ever. Instead of a JDK with a complex license, mixing both free and commercial features and containing field-of-use restrictions, Oracle now provides the JDK under a 100% free and open source license, or under a commercial license for those who wish to purchase a support subscription (and fund the development of OpenJDK).
Second, there are no longer major releases, and the new feature releases are similar to the old six-monthly "limited update". JDK 10, 11 and 12 are roughly the same size as 7u2 and 7u4, which also didn't get free security patches after six months. What's changed is the name given to those releases, and to make the updates cheaper and easier, they have been made more gradual, by allowing spec changes in feature releases. Not only do you get security fixes for free forever, but there are no more major upgrades.
So the main point of confusion is that some confuse the new feature releases with the old major releases, when, in fact, they are much closer to the old "limited update" releases. People see a new version number, see that that number is not freely supported beyond six months and panic, when, in fact, the old releases that were similar to the new feature releases were also not supported beyond six months. They themselves were considered "updates" to some major release, but major releases no longer exist, and the "updates" now get a new version number. See here [1] for a more complete explanation.
In addition, there's another new model, that allows organizations that for some reason need a much less gradual upgrade process than the new one -- and even less gradual than the old one -- and that is something that Oracle charges for. But because the JDK is now completely open source, other OpenJDK members have committed to backporting the fixes to provided a similar step-wise upgrade path for free.
(I work on OpenJDK at Oracle, but speak only for myself)
[1]: https://www.reddit.com/r/java/comments/bav1sy/winter_is_comi...
[0]: https://github.com/lima-vm/lima [1]: https://github.com/containerd/nerdctl