4 ms·
Man, this is so disappointing. Sure, there are probably businesses out there whose entire livelihood is built on akka, and I get that the creators might be ups
by Floegipoky 4y ago
Man, this is so disappointing.
Sure, there are probably businesses out there whose entire livelihood is built on akka, and I get that the creators might be upset that they're not contributing to the project. But there are a lot of other businesses out there where this might be a great solution for a very small part of the problem space, and they are just never going to use this tech now. A few years ago I used akka at my current gig for a project that ended up fizzling, and had always hoped to re-introduce it if another appropriate opportunity emerged. This change makes that a non-starter.
I also think this is a big blow in terms of the future of computing. The actor model is so useful, and it's taken so long to come close to mainstream. And now the biggest implementation shoves a giant stick in its own spoke.
- FromTheSteppe 4y agoThe biggest and most battle tested implementation is certainly Erlang OTP and not Akka. I'm actually happy more attention will be given to ol' boring Erlang now.
- Floegipoky 4y agoI guess I shouldn't have said that without checking, I'm not sure who's on top. My point still stands though. Most dev shops are already operating on the JVM, trying out akka was a much easier sell than adopting BEAM. Whether or not akka is more widely deployed than erlang, IMO akka was driving more adoption of the actor model.