News for hackers. Stuff that matters.

A comment on The Next Step for Generics. Parent comment

Re:The Next Step for Generics by bcrosby95 on Tuesday June 16, 2020 @07:02PM (#23545407)
Superficially they're very different. But lots of people use Go because its a "first class" concurrency language. Concurrency was given a huge consideration in Clojure too, with its immutability, STM, agents, etc. The reasons you might choose Go can overlap heavily with why you might choose Clojure, Erlang, or Elixir.
[ Parent | on HN ]
Re:The Next Step for Generics by vips7L on Tuesday June 16, 2020 @11:58PM (#23547606)
Is it really first class though? Anything CPU bound is basically a noop since GO doesn't have actual threads.
[ Parent | on HN ]
Re:The Next Step for Generics by bcrosby95 on Wednesday June 17, 2020 @12:22AM (#23547757)
Go automatically multiplexes goroutines on top of OS threads. You can peg all the cores of a multicore CPU in a single Go program using goroutines.

Edit: last I looked you could see how many OS threads would be used by looking at runtime.GOMAXPROCS. There was a time when it would just default to 1, but it looks like they changed it. When I last programmed in Go you had to override it via an environment variable or set it in code.

[ Parent | on HN ]