> I find that this article leaves the main question unanswered: what happened to just building a JAR? What happened is that the world has turned polyglot. Many

> I find that this article leaves the main question unanswered: what happened to just building a JAR? What happened is that the world has turned polyglot. Many of the things that Java pioneered in the wider industry have been resupplied in different places at different levels of the stack. Containerisation essentially creates uniformity for a lot of workflows. While Java has addressed all these concerns itself for a long time, the overhead of two build chains, two admin toolkits, two registries etc etc becomes increasingly onerous. Some folks will have a 100% Java mandate. This project is not for them. Others will have a 100% containers mandate. This project is for them.