[magnio]

I doubt Go has any sizable effect on the community of programming language developers. Probably Pascal has more impact on this.

[DetroitThrow]

Pascal has a lot of influence on this, but Go as well! My PL friends often talk about Go's benefits and flaws when thinking about advancing other their own projects or improving the mainstream languages they work on.

[Mawr]

Then you haven't been paying attention to the space. At all.

Every single new post-Go language, like Rust & Zig, ships with an opinionated autoformatter and a single go-to command to manage builds, packaging, etc.

And how many new languages do you see include inheritance and exceptions?

Older languages have started adapting what they can too:

- Python with `uv` and `black`

- Java with goroutine-like fibers and modern configuration-free gcs and the go-gc-like low pause times zgc

- Many languages now ship a production-ready http server, just like Go

[pjmlp]

Go has exceptions, bad ones at that.

From type theory exceptions are effects, and result types are a form of effects.

Auto formatting has been a thing in IDEs for a decade, and doing pre-commit hooks on CVS with indent was a thing in the 1990's.

Java and .NET had http servers.

Co-routines trace back to languages like Solo Pascal.

Configuration free GC not really that great, given the rewrites into Rust.

Anyway, Oberon, Modula-3, Eiffel, .NET,....

Pauseless GC goes back to real time Java from PTC, Aonix, Aicas, and companies like Azul with their custom hardware.