[kennywinker]

Go is a programming language. It’s not exactly pushing google’s ad agenda.

Your criticism of using github and discord are somewhat valid, but asking people to re-invent the wheel while they re-invent the bicycle seems like arbitrarily making up rules so everyone fails. Is there some influence you expect to leak into their platform thru github or discord?

[threethirtytwo]

They are standing on the shoulders of giants. There's nothing wrong with the ideals and the motivation, but it begs the question: Could Mu exist without go? could go exist without google? Could Mu exist without google?

And all of that culminates with: Could the level of technology and the internet reach the state it is today without big tech? And if not, was the price we paid to get here worth it?

[DoctorOW]

> but it begs the question: Could Mu exist without go? could go exist without google? Could Mu exist without google?

No, it doesn't.

Obviously Mu could exist without Go, if Google stopped development on the language, its current state could be forked (Go 2). Lots of programming languages exist without Google's support, there are even programming languages older than Google.

[threethirtytwo]

Woah didn’t know there were programming languages other than golang. Perhaps they can switch to nodejs, Google wasn’t involved with that.

[habbekrats]

go does push silly things. besides being overhyped, they block anonimizing tech when accessing package repos for example.

you dont want anything to do with google or anything they make or host. they will only do it to extract shit from you. they dont give nything dont be naive.

[uka]

C is also a programming language. Unlike go it foes not depend on a big tech company for it to live. No need to reinvent the wheel. Just use wheel that does not come with a big techh bagagge.

[treyd]

> It’s not exactly pushing google’s ad agenda.

Maybe not their ad agenda, but certainly one of their agendas. Specifically, the agenda they have to get young, inexperienced developers prepared for specifically the software development practices they employ internally.

It was directly stated that "Go is not for clever developers" and that their target is recent graduates with limited experience. It punishes you for trying to think about what you're building and to design sophisticated software, relying more on brute force. It doesn't encourage you to reach higher.

[hn_throw2025]

I don’t know where you are on your career journey, but having worked with countless clients, business domains, and projects as a freelancer I value readability over everything else.

If you’re working on a greenfield project in a team of one then I suppose it’s great to get in an expressive mood and emit your code poetry from those fingertips.

It’s very different to inherit a quirky puzzle and reverse engineer a mental model from there.

[kennywinker]

> Go is not for clever developers

What “clever” code is required to write a BBS-over-IP? 99.99% of code isn’t clever and shouldn’t be clever.

> It punishes you for trying to think about what you're building and to design sophisticated software, relying more on brute force.

Can you give an example of this? I have not written much go, so i am unable to think of a case where golang encourages brute force over sophistication?

[treyd]

FOSS projects have their constraints on time and usually not talent, like for-profit teams often are, so they should want the code they write to go farther.

They've explicitly stated that they wanted to discourage building abstractions, since "abstractions are hard to learn".

Concretely, this is evident in how channels and goroutines both poorly compose together, in part a result of the unsophisticated type system. It's difficult to build very generic libraries that can be leveraged as force multipliers, like the tokio-tower ecosystem does. You can do it, but it comes at performance costs or involves relying on codegen.

Google's Bazel build systems are designed around reasoning about and checking-in generated code, but the standard go tooling doesn't do this well and git workflows also don't really grapple with it well. This aspect of the design is very clearly an example of internal Google processes leaking out.