[valenterry]

> But sure, it makes it easier for programmers at all levels to get started, and to get real work done.

It is this condescending attitude that I feel many golang advocates (online) share that makes me shiver.

What are you implying, that devs using other languages don't get "real work" done?

Let's wait until Go has the same history, maturity and reach of e.g. Java and then let's see how well it will hold up in comparison.

[Mawr]

Start a Java project and a Go one.

In the time you get everyone on the team to agree whether you should use Maven or Gradle, which testing framework to use, or figure out how to autoformat your code, your Go program will be done.

[umanwizard]

Meanwhile, start a rust project, and:

* everyone agrees to use Cargo

* everyone agrees to use `cargo test` (what even is a “testing framework”)?

* everyone agrees to use `cargo fmt`

What’s the advantage of go here?

By the way, the formatting situation is actually worse in Go because there are both gofmt and gofumpt used in the wild, at least gofmt has different behavior depending on different flags, and there are additional linters people use to e.g. ban long lines that for some reason the formatters don’t cover.

[Mawr]

Yes, Rust copied all those good ideas from Go, so this is an odd argument to use.

I don't know why we're talking about Rust in the first place, but an obvious advantage would be compilation time and iteration speed in general.

[vessenes]

The rust team will be bikeshedding a borrow checker error and debating if using unsafe is appropriate for some time after this, though.

[valenterry]

Well, sure.

Let's wait another 15 year and then compare the new languages at that time against golang. Then let's see how golang is doing in comparison.