scala/akka 或 go 更适合解决的问题
最近研究 Go 时，似乎可以将 Go 和 Scala/Akka 进行类比， 其中 akka Actor 类似于 goroutine，ActorRef 类似于 Go 通道。
除了平台类型问题（JVM 或非 JVM）之外，还有哪些功能差异会导致人们选择其中之一？
In looking into Go recently it seems like one could analogize between Go and Scala/Akka,
where an akka Actor is similar to a goroutine and an ActorRef is similar to a Go channel.
Other than platform type issues (JVM or not) what are the functional differences that would lead one to choose one or the other?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
免责声明：我是 Akka 的产品所有者，
您可能可以在 goroutine 和通道之上实现 Actor 模型，
但我将它们视为两个截然不同的抽象层。
对于选择者来说，问题几乎可以是任何问题，但这里有一些建议：
如果有人知道是否有 Golang 的 Actor Model impl，我会喜欢一个链接。
Disclaimer: I am the product owner of Akka
You could probably implement the Actor Model on top of goroutines and channels,
but I see them as two distinctly different layers of abstraction.
Questions for the person choosing could be virtually anything but here are some suggestions:
If someone knows if there is an Actor Model impl for Golang I'd love a linky.
我感觉Scala/Akka更成熟一些。有更大的使用社区和更多的动力。
其他人不会同意，但对我来说，Go 仍然感觉像“我也是”，而且我不会用“我也是”语言编写任何严肃的东西。
I feel like Scala / Akka is more mature. There is a bigger use community, and more momentum.
Other people won't agree, but to me Go still feels like a "me too", and I would not code anything serious in a "me too" language.