That's directly relevant to my life, since I hope someday to bring #Querki into the modern age, using CE3 and fs2, and it's 100% based on Akka Cluster Sharding. (Still the number-one use case for Akka.) So that's going to get bookmarked for future reference; thanks!
They grow up so fast! #PlayFramework has released version 3.0. It is using something I have never heard of and that is #ApachePekko which is a fork of #Akka 2.6. Pretty exciting stuff all around. #Scala
Apache #Pekko is replacing #Akka in Play Framework ❤️😍
I really wish Lightbend well, I hope they thrive, but blowing up the FOSS ecosystem around Akka was a foreseeable consequence of its licensing turning proprietary. All FOSS projects will predictably move to Pekko, and Pekko isn't a drop-in replacement (due to the inevitable change in packages), which puts Akka in a very tough spot.
N.b., version 2.9 is probably the last release with support for Akka.
Dust hasn't settled yet on Apache #Pekko, but I really believe it will thrive.
This is the true power of #FOSS. When you don't agree with the direction, you can fork from the last adequate version! Resources are required, but where there's a need, there's a way 💪
Furthermore, in the case of Pekko, #Apache was the best organization to take this on because they have adequate processes that give credibility to such forks.
When I've taught people the #actor model (usually with #akka) the hardest thing I've seen is convincing people to not break the rules.
It's one reason I started favoring the 'm behavior -> 'm -> unit -> 'm behavior version of the model: it makes it more explicit how you can manage state and opens the conversation immediately about "this is how you can do this" as opposed to hiding it behind an other API call (become) where people can default to old patterns that break the actor assumptions.
This is the 2nd of such moves this year to my knowledge; first there was #Lightbend and #Akka and now this. What a year for #FOSS 😕
I know for a fact that so many organisations use #hashicorp products for commercial purposes w/o ever contributing back. And I understand how this may feel for hashicorp in these harsh economic times. Though this still is, IMHO, a cheap move: they used an OSS license for a very long time which resulted in a massive user base and a “soft” vendor lock-in, and now they decided to milk that user base.
Looking forwards to solid community-driven forks of their products 💪
HashiCorp changes license from Mozilla Public License 2.0 to Business Source License 1.1 on their products (www.hashicorp.com)