3 ms·

Quite typical of golang pushing more complexity onto the user in order to save complexity in the compiler, then claim that golang is a "simple" language shrugs.

by azth 5y ago

zarzavat 5y ago
While it’s fun to hate on Go and the language has indeed made some bizarre design choices, the fact that there’s even a market for Go shows that there’s some major deficiencies in other languages. If Go is really so bad, why don’t Go programmers use e.g. Rust? I’m sure they’d cite things like: - Compilation time is much faster in Go. - Complexity. Rust is a highly complex language even for me as a C++ programmer. For those who are new to compiled languages they are certainly going to choose Go over Rust - GC definitely has development time benefits over a borrow checker if you can afford the extra CPU headroom and memory usage - Go’s concurrency model is more appealing to many people The real question is, why is there not a “Go but designed by sane people” language?
- azth 5y ago
  golang doesn't really compete with rust, but it's more like a faster python/ruby/js. You can see this by the companies that have moved over from those languages to golang. Hype definitely plays a role, but also the perception that it's quick to pick up, and does decently well when it comes to performance. > The real question is, why is there not a “Go but designed by sane people” language? The fact is that the JVM and .NET platforms would almost surely do better for anything that golang is considered for, but there's a lot of hype and companies want to attract programmrs.
- kaba0 5y ago
  The real question is why not just use Java, C#, D, Haskell, Js or the myriad other managed languages? Rust is complex due to the inherent complexity of being a low-level language.
philosopher1234 5y ago
Let’s not be so simple minded. Users bear some of the cost of complex compilers, too. And complex languages, even if they make writing some code simpler, ALWAYS have a cost. It’s a balance, there’s not an obvious right answer.

Quite typical of golang pushing more complexity onto the user in order to save complexity in the compiler, then claim that golang is a "simple" language shrugs.

by azth 5y ago

Quite typical of golang pushing more complexity onto the user in order to save complexity in the compiler, then claim that golang is a "simple" language shrugs.

zarzavat 5y ago

While it’s fun to hate on Go and the language has indeed made some bizarre design choices, the fact that there’s even a market for Go shows that there’s some major deficiencies in other languages. If Go is really so bad, why don’t Go programmers use e.g. Rust? I’m sure they’d cite things like: - Compilation time is much faster in Go. - Complexity. Rust is a highly complex language even for me as a C++ programmer. For those who are new to compiled languages they are certainly going to choose Go over Rust - GC definitely has development time benefits over a borrow checker if you can afford the extra CPU headroom and memory usage - Go’s concurrency model is more appealing to many people The real question is, why is there not a “Go but designed by sane people” language?

azth 5y ago
golang doesn't really compete with rust, but it's more like a faster python/ruby/js. You can see this by the companies that have moved over from those languages to golang. Hype definitely plays a role, but also the perception that it's quick to pick up, and does decently well when it comes to performance. > The real question is, why is there not a “Go but designed by sane people” language? The fact is that the JVM and .NET platforms would almost surely do better for anything that golang is considered for, but there's a lot of hype and companies want to attract programmrs.
kaba0 5y ago
The real question is why not just use Java, C#, D, Haskell, Js or the myriad other managed languages? Rust is complex due to the inherent complexity of being a low-level language.

philosopher1234 5y ago

Let’s not be so simple minded. Users bear some of the cost of complex compilers, too. And complex languages, even if they make writing some code simpler, ALWAYS have a cost. It’s a balance, there’s not an obvious right answer.