Hi Eirik,

8 apr 2014 kl. 14:53 skrev Eirik <[email protected]>:

> Great that you improve the API inspired by rxjava.
> 
> However you should have handled the transition to the new API better. You 
> should have deprecated the module in 2.3.
> 
> Just removing the entire experimental feature is kinda f u to developers who 
> have built on it, but don't want to stay on 2.2 anymore for whatever reason.

Please refrain from using offensive language on this list.

> Yeah, I know it's an experimental feature, but if this is how experimental 
> features will be handled in the future it's not very tempting to use them at 
> all until they eventually make it past experimental.

The release of Akka 2.4 is quite a while out (precise details will be 
forthcoming, but we might not correlate it with the availability of the HTTP 
module). This means that keeping the Pipeline infrastructure around would have 
meant that many more people would waste a lot of time trying to figure it out 
while it is effectively dead already.

As to removal: of course we have not removed Akka 2.2 Pipelines (since that is 
impossible), we just did not ship the code with 2.3. This is an open source 
project, which gives you all the power to copy the source files into your build 
and use them if you want to.

Regards,

Roland

> 
> -Eirik
> 
> 
> 
> On Thursday, January 16, 2014 11:08:34 PM UTC+1, rkuhn wrote:
> Dear hakkers,
> 
> the first release candidate for Akka 2.3.0 is waiting just around the corner, 
> and as the subject says, the Pipeline infrastructure in our shiny new Akka IO 
> package, which was introduced in version 2.2.0, will be discontinued. The 
> whole IO subsystem was marked “experimental” throughout the 2.2.x series and 
> unfortunately this part of the experiment did not work out: the API is just 
> too clunky and unintuitive.
> 
> We have something brewing which will be more than just a replacement for 
> Pipelines: inspired by RxJava we are working on implementing Reactive Streams 
> for Akka which will allow declarative transformation of streaming data of all 
> kinds, with proper handling of back-pressure and of course fully typed. This 
> will hopefully be available for preview in a few weeks and it will be 
> included in the 2.4 milestones as soon as it is ready. Doing IO with this 
> abstraction will be a breeze.
> 
> So instead of keeping Pipelines in a zombie state and luring people into 
> their dead arms we decided to cull them early. For those of you who need some 
> fresh Akka but also want to stay on Pipelines for the time being we will 
> release a bugfix release 2.2.4 very soon as well.
> 
> Regards,
> 
> 
> Dr. Roland Kuhn
> Akka Tech Lead
> Typesafe – Reactive apps on the JVM.
> twitter: @rolandkuhn
> 
> 
> 
> -- 
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: 
> >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.



Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn


-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to