@Sciss, very similar? Are you serious? Well, both implement Reactive Streams, so both are about back-pressured non-blocking asynchronous stream processing. But in my opinion the differences listed on the slide you mention are significant, in particular Swave's non-lifted approach (including the absence of materialized values) and the possibility to run synchronously. Maybe the "focus point" slide also helps with the difference: http://swave.io/scaladays/2016/#/2
@hseeberger Yes I have seen the slides. Well, similar from my perspective. In my scenario, I have a separate persistence layer before I build the blue-print, so the lifted/non-lifted is irrelevant in my case, as are the materialised values since I have to anyway track all graph nodes separately.
I mean there must be some kind of motivation to write Swave, things the author didn't like about Akka Streams
Don't get me wrong. I think it's great to have multiple frameworks. It's just that now I'm building a prototype, I don't want to make the mistake to tie it too closely to one implementation when the other would potentially offer me more benefits. In my case I have to implement a lot of custom GraphStageLogic, so it becomes really tied to the low level API. So I'm just trying to elicit whether I should look more closely at the Swave architecture, that's all
For instance, does Swave require Java 8 or is it compatible with Java 6?
Are there plans for Scala.js, those kind of things