Hello, author here! I'm happy to answer any questions.
Adding Go support was an interesting decision for us because Go tooling is already quite excellent, whereas Python and Shell don't have as strong of a story. We tried to be honest with what Pants's strengths and weaknesses are so that Pants can augment Go with some unique benefits like being able to run `./pants --changed-since=HEAD fmt` (integration with Git). I'm definitely curious to hear any feedback!
The #welcome channel in the Pants community Slack (https://pantsbuild.slack.com) is the best place to discover what large companies are using Pants 2, including Fortune 500 companies.
I'm preparing to launch a series of user interviews on our blog (https://blog.pantsbuild.org/) in coming weeks. Those in-depth conversations explore things like how the Pants 2 adoption process has gone, benefits their team is experiencing on the ground, pragmatic comparisons with alternate solutions the company has used or evaluated, etc.
Adding Go support was an interesting decision for us because Go tooling is already quite excellent, whereas Python and Shell don't have as strong of a story. We tried to be honest with what Pants's strengths and weaknesses are so that Pants can augment Go with some unique benefits like being able to run `./pants --changed-since=HEAD fmt` (integration with Git). I'm definitely curious to hear any feedback!