Yeah, I worked with a guy in the late 2010s - one of the most painful people I've ever worked with - who would tell anyone that would listen that Go (as it was in 2018) was the perfect programming language - it had all the features you'd ever need - no more, no less. It doesn't need generics, the package management story is fine etc. Thankfully he's been out of my life for a long time now but I believe he's still writing Go, and I bet that he's telling anyone that will listen that Go (as it is in 2026) is the perfect programming language and that its implementation of generics was necessary and perfect etc.
He wasn't the only one but he certainly took it to the extreme.
This is an outlier. The Go team and community never endorsed that. In fact, their position has always been the opposite. To give just one example, see [1].
I think it’s pretty clear this post was a response to the clear dogma within the community.
> But we need help from everyone. Remember that none of the decisions in Go are infallible; they’re just our best attempts at the time we made them, not wisdom received on stone tablets.
I mostly frequent smaller subreddits with at most a handful of mods for niche subjects and it's great. Then when I occasionally need to ask a question in a bigger one... out come the mods who live for the rules.
Agreed. I remember a couple of years ago raising an AWS support ticket and eventually got an answer about it being some undocumented limitation in Aurora Serverless v1. Now I get equivalent of googling my question before I can even raise a ticket.
Gosh, that's kind of sad. I hate having to wait 12 to 24 hours for an answer from AWS support - there's no way I'm raising the ticket without exhausting all avenues from my end.
> Businesses I've spoken to hate the idea of moving their code forge. Migrations like that suck and they're expensive. There isn't a meaningful differentiator between the other managed options, so the goal would just be to stand still. Unless GitHub's stability spirals fast I don't see a big wave of businesses leaving.
Yep, been through a somewhat pointless GitHub to GitLab migration because, at the time, GitLab was cheaper. Now GitHub is cheaper again and the migration was a big annoying and expensive project.
I remember working at a company with at least 5,000 repos across five or six GitHub orgs, plus more stuff in Perforce.
Probably some old experiments in there but the company had its fingers in a few pies and some departments didn't mind creating yet another service to solve a problem.
I definitely archived the old stuff in my department (we had eight repos and that felt like enough for three people).
Gosh, haven't heard of Domo in years. I remember a previous company used it but I never had anything to do with the implementation. Based on some of the other silliness that company bought into, this now makes sense.
He wasn't the only one but he certainly took it to the extreme.
reply