No, it's not a platform, unless you want to redefine platform to mean "something with lots of supporting tools", instead of "something that other things run on top of".<p>We would have to call pretty much all languages platforms if so. The list of things called out is not unique in any way to Go.
It's very similar to Java and the JVM in many ways. Curly braces, garbage collected, strong typing, etc. Which raises the question, if you could level up the Go platform with a more modern language where e.g. generics and typing are less awkward & verbose. For Java there have been a few languages that provided that. I'm doing a lot of Kotlin the last few years for example. Other languages are available.<p>And of course with a native compiler now maturing, Kotlin is increasingly becoming more suitable for exactly the kind of stuff Go is being used for. I've not done a lot with Go but enough to not be too impressed with it as a language. I'm more impressed with it as a platform though. So much so that I might tolerate the language even. I appreciate the wide availability of good libraries and components out there. The build tools. Great decisions to make formatting mistakes a compilation error, etc. There's a lot to like. But the language as such is a bit bare bones and somewhat verbose especially for things like error handling. IMHO the comparison with Java is actually very fair in that sense since it is also a bit dated and clunky at this point.<p>Whether Kotlin or some other language (Zig?) gets more popular for native development is of course an open question but there's no good reason why system programmers should not have more access to more modern language features.
It's a bit of a stretch because half of the tools are not part of the Go distribution, for instance IDEs like Jetbrains or VS Code. Also, other languages do have IDE support as well :) Other examples are Delve, SBOM generation tools or Sonar code scanning.<p>It's nice that Go includes a tool for finding race conditions or vulnerability checking with govulncheck but the overall claim is more marketing than a factual assessment of "Go".
Not sure what makes a platform, but I found interesting that you can easily re-use packages from other repositories without having to explicitly be published as libraries
> Compatibility Promise: This makes choosing Go much safer, especially for companies, as it avoids the need for significant future refactorings, as happened from PHP 4 to PHP 5 or from Python 2 to Python 3, for example—more details on the language blog.<p>Wait until it is time for Go2.0. until then it is comparison of minor vs. major versions.<p>Overall, this is not a platform description. This is fanboying over ecosystem richness. I'm glad for the author that they've found something they like, but they are a bit off the mark in the post.