-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Pekko instead of Akka #105
Comments
Good point, but maybe we should wait for a first release. |
Update: "porting" the akka code to pekko is a misnomer: it's actually trivially simple! So, we just need to decide if we want to do it or not. Or we we turn it into an exercise (although it's not Scala 3 specific). |
I am in favor of porting to Pekko. It is better if we use the latest version of a library, but the latest version of Akka is under business source license. |
Porting to Pekko is very easy. We could even make it an exercise. WDYT? |
I think we should focus on the migration to Scala 3, and exclude the migration to Pekko from the exercises. Otherwise it could be misinterpreted as: "We need to migrate to Pekko because of Scala 3". We can explain the difference between Pekko and Akka, and the reason why we chose Pekko. We can explain that it is really easy to migrate from Akka to Pekko, but more as a side note than an exercise. |
Makes sense. I'll migrate from Akka to Pekka then. Also need to change references to Akka to Pekko in the slide deck. |
Because Akka is not open source anymore maybe the course should use Pekko, which is the open source fork of Akka, but Pekko is not yet released.
The text was updated successfully, but these errors were encountered: