It's worth pointing out that the example you linked with the cdecl is not showcasing the swift-java interoperability but using "raw" JNI patterns as if you would do it with C. This example does showcase the…
Hi there (ex Akka core team here). Yeah there's slight differences what the main concept is in those libraries. It kind of boils down to Akka's concept of an actor being more low level, and then adding the capabilities…
(disclaimer: Akka team here). The post, somewhat surprisingly, omits to mention Akka Streams (which is a perfect fit, since, as the post mentions 'The data came through a stream [...]'), and Reactive Kafka (which is an…
Typesafe/Lightbend continues to back Scala as it always did, no change there. Scala Center is a great additional move to get additional people / resources to work on Scala :-) So while "the recent typesafe news" are…
Nice. gonna show some git tricks to my colleagues using it :-)
It's worth pointing out that the example you linked with the cdecl is not showcasing the swift-java interoperability but using "raw" JNI patterns as if you would do it with C. This example does showcase the…
Hi there (ex Akka core team here). Yeah there's slight differences what the main concept is in those libraries. It kind of boils down to Akka's concept of an actor being more low level, and then adding the capabilities…
(disclaimer: Akka team here). The post, somewhat surprisingly, omits to mention Akka Streams (which is a perfect fit, since, as the post mentions 'The data came through a stream [...]'), and Reactive Kafka (which is an…
Typesafe/Lightbend continues to back Scala as it always did, no change there. Scala Center is a great additional move to get additional people / resources to work on Scala :-) So while "the recent typesafe news" are…
Nice. gonna show some git tricks to my colleagues using it :-)