if you need more recent gpars documentation, i'm working on v2.0 of it that you can see here: http://gpars.aws.ie.a9sapp.eu the download page does show gpars 2.0 but it's just copies of 1.2.1 that i've renamed as placeholders. since jsr-166Y may be dropped there are a number of gpars features that may disappear, so we're hoping to clarify this issue before summer release. 😊
On 16 March 2017 at 23:13, Jochen Theodorou <blackd...@gmx.org> wrote: > On 16.03.2017 22:54, Jochen Theodorou wrote: > >> On 14.03.2017 12:06, Russel Winder wrote: >> [...] >> >>> It might be worth thinking about whether GPars has a real future since >>> so few people seem to be interested in actively working on it. With >>> Quasar (Parallel Universe thing not Quasar Framework) there is a >>> fibers, actors, CSP framework with resources behind it. OK so no proper >>> dataflow out of the box, but it could be added. >>> >> >> you mean http://www.paralleluniverse.co/quasar/ ? >> Fibers there work based on agents and bytecode rewriting? CSP I have not >> seen, but I did not look to closely. License wise it might be ok, since >> it offers EPL 1.0 dual with GPL3 (the later would not be ok for us). >> >> But frankly, if I am right about the fibers, then this part is no option >> for me. That leaves the CSP part, which I did not see and actors. Is it >> really worth it then? >> > > found Dataflow, reactive streams and channels now... also that it seems to > have a dependency on Guava... nothing against Guava itself, but there are > too many incompatible version going around and it is a big dependency of > over 1MB > > bye Jochen > >
