News for hackers. Stuff that matters.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by whimsicalism on Tuesday July 18, 2023 @12:06PM (#36774717)
Go was successful because it came after decades of pretty much no language putting good networking tools in their stdlib.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by ilyt on Tuesday July 18, 2023 @12:29PM (#36775144)
Not just networking but focusing on concurrency.

In before if you needed to make a highly concurrent network app you had to get into asynchronous programming that generally makes code looks shit (or at least slightly worse) and harder to debug.

With Go and goroutines taking IIRC around 8k for start you can "just" spawn as many of them as there are connections and write your code as if it was serial one. Add some half-decent concurrency primitives and it's pretty easy to not fuck up highly concurrent and highly parallel code.

Re:Ten Years of “Go: The Good, the Bad, and the Meh by codyb on Tuesday July 18, 2023 @01:12PM (#36775902)
Erlang's been around forever, also a fairly simple language. I'd imagine concurrency's easier than on Go.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by macintux on Tuesday July 18, 2023 @01:12PM (#36775907)
Erlang had a better concurrency story than Go, and better error handling. But alas marketing wins.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by drBonkers on Tuesday July 18, 2023 @01:52PM (#36776605)
Erlang is dynamically typed.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by macintux on Tuesday July 18, 2023 @02:36PM (#36777266)
True, and Go has a much better story in some other areas, but “…if you needed to make a highly concurrent network app you had to get into asynchronous programming that generally makes code looks shit” is inaccurate.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by arcanemachiner on Tuesday July 18, 2023 @03:03PM (#36777640)
The process of bringing types to Elixir is officially underway:

https://elixir-lang.org/blog/2023/06/22/type-system-updates-...

It's not Erlang specifically, but it is a BEAM language, so tomato tomahto.

Re:Ten Years of “Go: The Good, the Bad, and the Meh by aptenoforst on Tuesday July 18, 2023 @03:16PM (#36777809)
This doesn't say much because people generally throw interface{} everywhere.

Go is used because Google and that's it.

Re:Ten Years of “Go: The Good, the Bad, and the Meh by jerf on Tuesday July 18, 2023 @03:19PM (#36777852)
No, they don't. They didn't before generics and they do even less now.

You can tell this is an accusation thrown around by non-Go programmers because frankly, throwing around a lot of interface{} was always really inconvenient. It's not something the language trains you to do... it's something you get punished for, really quite hard.

Re:Ten Years of “Go: The Good, the Bad, and the Meh by jerf on Tuesday July 18, 2023 @03:18PM (#36777828)
Erlang, frankly, has a lot of problems. The first major thing I used Go to do in the 1.4-1.6 era was to migrate my multi-year production Erlang system to Go, and I never looked back.

Somehow Erlang gets this special dispensation where people get to talk about it as if it's still 2005 and it's still this unique and interesting snowflake with virtually no competition. Which it was... back then. But having successfully convinced the world that there's an interesting space there, in 2023 there's a ton of options and the point in that space Erlang staked out isn't actually that interesting or unique when you measure it by 2023 instead of 2005.

Re:Ten Years of “Go: The Good, the Bad, and the Meh by drBonkers on Wednesday July 19, 2023 @06:09PM (#36794167)
I agree with you. Are there languages beyond Go that you would measure Erlang against in the dimension of concurrency ergonomics?
Re:Ten Years of “Go: The Good, the Bad, and the Meh by Mawr on Tuesday July 18, 2023 @06:47PM (#36780058)
Marketing, lol. Erlang is a functional language. Functional. That alone has prevented its widespread adoption.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by lenkite on Wednesday July 19, 2023 @01:09PM (#36789784)
Erlang needs a VM. Not statically typed. Poor compute performance. Poor strings.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by etiennedi on Tuesday July 18, 2023 @12:25PM (#36775067)
Not sure if that alone is what made Go successful. But yes, having great networking tools in the stdlib is very refreshing! One of the things Go got right.
Re:Ten Years of “Go: The Good, the Bad, and the Meh by za3faran on Tuesday July 18, 2023 @01:55PM (#36776643)
The google brand name behind it also definitely played a role.