These are chat archives for sirthias/swave

28th
Jun 2016
Heiko Seeberger
@hseeberger
Jun 28 2016 04:38
@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
Hanns Holger Rutz
@Sciss
Jun 28 2016 10:21
@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
Konrad `ktoso` Malawski
@ktoso
Jun 28 2016 10:22
listen to the talk again Hans ;)
more points: extensability is another thing, extending akka streams with your custom things is trivial and "feels native", it's something we specifically designed for ;)
Mathias
@sirthias
Jun 28 2016 10:22
@sciss It's true that swave and akka-stream do occupy roughly the same space.
However, the space is still quite new and a lot of it is still undiscovered.
Konrad `ktoso` Malawski
@ktoso
Jun 28 2016 10:23
I think it's healthy to have friendly competing implementations ;) we can learn stuff from one another :-)
Mathias
@sirthias
Jun 28 2016 10:24
We are still (as a community) figuring out how to work best with streams. E.g. with regard to emerging patterns, useful operators/transformations, implementation choices, etc.
With several somewhat-competing implementations we can explore the space together, from differing angles at the same time.
Hanns Holger Rutz
@Sciss
Jun 28 2016 10:26
@ktoso iss the talk online?
Mathias
@sirthias
Jun 28 2016 10:26
Reactive Streams (and stream processing in general, esp. but not only on the local node) is far too sexy to simply leave it all to the akka team! :)
@sciss The video not yet, AFAIK.
Hanns Holger Rutz
@Sciss
Jun 28 2016 10:28
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
Mathias
@sirthias
Jun 28 2016 10:29
@sciss Swave requires Java 8, as does Akka 2.4.x (if I'm not mistaken)
Otherwise I wouldn't recommend swave for any serious work at this point. It simply isn't quite ready yet.
Hanns Holger Rutz
@Sciss
Jun 28 2016 10:30
Ok
Well, I keep following the project in any case, looks exciting!
Mathias
@sirthias
Jun 28 2016 10:30
Re scala.js: sirthias/swave#6
Thank you!
Hanns Holger Rutz
@Sciss
Jun 28 2016 10:45
Just found this presentation: https://www.youtube.com/watch?v=0jq0-Ph2gpM
Can I ask what editor you are using for the live demo?
Mathias
@sirthias
Jun 28 2016 11:50
Just IntelliJ IDEA in presentation mode.
And: The talk from scalarconf in warsaw wasn't as good as the one from the scaladays, both content- as well as delivery-wise.
Anyway... :)