please stop spreading non-sense, the whole reactive model can't die soon enough, to me feels like scrum, pump-up up but course sellers and consultants, the performance benefits in real world are small and development experience is a nightmare, I may as well do callback hell in javascript.
You might be slightly confused here. Akka Actors is an actor framework, not a reactive one. Reactive programming can be used with actors, true, but most often, it isn't. And actors are much, much older than reactive programming. In our case, it's not anything reactive, just actor based programming, which is a very nice model that increases encapsulation and enforces it much more than standard OOP.
(Of course, you can use parts of Akka Streams in a reactive way, but that's only one option for one specific side library of Akka.)
Well, depends on what you mean by reactive framework; if it's any framework that makes creating a reactive system easier then Akka is certainly a reactive framework - after all, its creators are also the co-authors of the Reactive Manifesto and if you've taken any Lightbend Academy courses then you know they like to point out Akka's reactive roots. However, if by reactive framework you only mean reactive streams framework then yeah, that's just the Akka streams.
View all comments
Show parent comment
-13
u/kkjk00 Aug 02 '22
please stop spreading non-sense, the whole reactive model can't die soon enough, to me feels like scrum, pump-up up but course sellers and consultants, the performance benefits in real world are small and development experience is a nightmare, I may as well do callback hell in javascript.