If "you" are a one-man shop, that's fine.

If "you" are the legal department for a company with 10,000 developers, the GPL is scary. You can either blanket-ban GPL code, and make your life easy, or create a system for separately evaluating the use of each and every piece of GPL code you allow in, plus some auditing process to catch cheaters (who check in GPL code as their own work, which happens).

Cloud services companies usually go with the latter: because you don't have to share your code if you don't distribute it, the payoff is good to allow use of GPL code, and police the corner cases where you do distribute code. Blanket bans on GPL code are still common at old-school software companies.

It is a shame that this got submitted before we actually published the code. It is Easter and many of our engineers are taking these days off.
The release notes are also incomplete and not ready for publishing
Miguel

THIS IS A DRAFT OF THE 4.0 RELEASE NOTES

Windows won using abusive monopolist tactics.....

Java became de-facto monoculture, there is only one widely used implementation.

Javascript itself is a plugin. Any concept of distinction is flawed. Lets say in the panaea of worlds, Oracle gave Java tech and all its reference impl's away for free BSD styled. What if anything would be the harm of writing browser scripts in Java vs. Javascript vs. go vs. .net-whatever, etc.. if every single browser developer had access to native embeddable runtimes embedded into the tool?