|
Yes, because Ant exists since 2000, Maven exists since 2004, and MSBuild since 2003. Before it was a common procedure to have central package management, we used to store libraries (jars and dlls), on source control directly in some libs folder. Afterwards, even with central package management, enterprise software when done right, is not calling the Internet in every build, rahter there are internal repositories that are curated by legal and IT, and only those packages are allowed to be used in projects. So the tooling is naturally around after 20+ years, no one is doing YOLO project management when playing with customer's money. As for the "...latest version of the SDKs..", that is moving the goal posts, there is no mention of it on, > Go is the only language where I've come back to a nontrivial source code after 10 years of letting it sit and have had zero problems building and running. That alone, for me, more than makes up for its idiosyncrasies. |
For example, I worked on a project that just stopped being able to be built with Maven one day, with no changes to the JVM version, any of the dependencies, or the Maven version itself. After a while I gave up trying to figure it out, because the same project was able to be built with Gradle!
Older Scala projects were a pain in the ass to build because the Typesafe repositories stopped accepting plain HTTP connections, requiring obscure configuration changes to sbt. I've never had to deal with things like that in the world of Go.