英文:
Problems for which scala/akka or go are a better fit
问题
最近我在研究Go语言时发现，可以将Go和Scala/Akka进行类比。在这个类比中，akka Actor类似于goroutine，而ActorRef类似于Go的channel。
除了平台类型问题（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?
答案1
得分: 10
免责声明：我是Akka的产品所有者。
你可能可以在goroutines和channels之上实现Actor模型，但我认为它们是两个完全不同的抽象层。
选择者可能问的问题几乎可以是任何问题，但以下是一些建议：
- 开发/部署平台？
- 重用其他库和/或语言的可能性/愿望？
- 远程通信/集群？
- 开发环境/基础设施
- 开发人员的可用性
- ...
如果有人知道是否有适用于Golang的Actor模型实现，我会很高兴得到一个链接。
英文:
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:
- Dev/Deployment platform?
- Possibility/desire to reuse other libraries and/or languages?
- Remoting/Clustering?
- Development environment/infrastructure
- Availability of developers
- ...
If someone knows if there is an Actor Model impl for Golang I'd love a linky.
答案2
得分: -3
我觉得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.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论