Go is built around shared mutable state, which means when it comes to building correct concurrent programs it's no better than @celluloidrb
@timbray in my experience as the maintainer of an actor framework that runs atop a shared mutable heap, this is not the case
-
-
@bascule My first Go app had tons of concurrency and it was so easy/straightforward to use chan/go, no temptation to mutable state. -
@timbray you were still using shared mutable state -
@bascule I disagree. All the computation is in a goroutine which reads from a chan & writes to a chan. -
@timbray if you write a program that never mutates state that's fine ;) -
@bascule My point is, Go makes that easy AND all the samples/best-practices push you in that direction. -
@timbray it's "easy" to write a program that doesn't mutate state if you're trying. Ruby makes it easy too. It prefers copying over mutation -
@bascule Ruby lacks the idiomatic support that Go provides. Hey, I still prefer writing Ruby. But I really liked Go’s Erlang-y idioms.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.