is more concerned with Google's interests than good engineering August 1, 2020 on Drew DeVault's blog sucks. It’s certainly prettier than, but under the covers, it’s a failure of engineering characteristic of the Google approach.

Go is a pretty good programming language. I have long held that this is not attributable to Google’s stewardship, but rather to a small number of language designers and a clear line of influences which is drawn entirely from outside of Google — mostly from Bell Labs. provides renewed support for my argument: it has all the hallmarks of Google crapware and none of the deliberate, good engineering work that went into Go’s design.

It was apparent from the start that this is what it would be. was launched as a closed-source product, justified by pointing out that is too complex to run on an intranet, and has the same problem. There are many problems to take apart in this explanation: the assumption that the only reason an open source platform is desirable is for running it on your intranet; the unstated assumption that such complexity is necessary or agreeable in the first place; and the systemic erosion of the existing (and simple!) tools which could have been used for this purpose prior to this change. The attitude towards open source was only changed following’s harsh reception by the community.

But this attitude did change, and it is open-source now1 2, so let’s give them credit for that. The good intentions are spoilt by the fact that fetches the list of modules from a closed-source proxy through which all of your go module fetches are being routed and tracked (oh, you didn’t know? They never told you, after all). Anyway, enough of the gross disregard for the values of open source and user privacy; I do have some technical problems to talk about.

One concern comes from a blatant failure to comprehend the fundamentally decentralized nature of git hosting. Thankfully, is supported now4 — but only the, i.e. the hosted instance, not the software. hard-codes a list of centralized git hosting services, and completely disregards the idea of git hosting as software rather than as a platform. Any GitLab instance other than (such as or; any Gogs or Gitea like Codeberg; cgit instances like; none of these are going to work unless every host is added and the list is kept up-to-date manually. Your intranet instance of cgit? Not a chance.

They were also given an opportunity here to fix a long-standing problem with Go package discovery, namely that it requires every downstream git repository host has to (1) provide a web interface and (2) include Go-specific meta tags in the HTML. The hubris to impose your programming language’s needs onto a language-agnostic version control system! I asked: they have no interest in the better-engineered — but more worksome — approach of pursing a language agnostic design.

The worldview of the developers is whack, the new site introduces dozens of regressions, and all it really improves upon is the visual style — which could trivially have been done to The goal is shipping a shiny new product — not engineering a good solution. This is typical of Google’s engineering ethos in general. sucks, and is added the large (and growing) body of evidence that Google is bad for Go.

  1. Setting aside the fact that the production site is amended with closed-source patches. ↩︎

  2. The GitHub comment explaining the change of heart included a link to a Google Groups discussion which requires you to log in with a Google account in order to read.3 If you go the long way around and do some guesswork searching the archives yourself, you can find it without logging in. ↩︎

  3. Commenting on Go patches also requires a Google account, by the way. ↩︎

  4. But not! ↩︎

Articles from blogs I read Generated by openring

WASI support in Go

Go 1.21 adds a new port targeting the WASI preview 1 syscall API

via The Go Blog September 13, 2023

Finding Domains That Send Unactionable Reports in Mastodon

One of the things we struggle with on is un-actionable reports. For various reasons, most of the reports we handle are for posts that are either appropriately content-warned or don’t require a content warning under our content policy–things lik…

via Aphyr: Posts September 3, 2023

Summary of changes for August 2023

Hey everyone! This is the list of all the changes we've done to our projects and apps during the month of August. We'll also be reporting in our on position in the world, and on our future plans. Summary Of Changes, added Heriot Bay, Balle…

via Hundred Rabbits September 1, 2023