Hi Guido, with Java 8 lambdas and Scala 2.12 we will indeed be able to unify the experience (and API) more, but there are other issues that won't go away, for example the different collection APIs. In terms of Futures the jury is still out on what the Java world will settle on, but the answer will probably not be Scala Future. So, we will have to continue to offer different APIs for the two languages for the foreseeable future.
Regards, Roland Sent from my iPhone > On 06 Jun 2015, at 20:41, Guido Medina <[email protected]> wrote: > > Hi, > > I have been using Akka now for three months now and one thing that got my > attention in a very good way is the fact that you can use Scala methods and > functions from Java, then I wonder: > Is it really necessary to have an Akka Java API for Java developers in > general? > I have not much experience with Java-to-Scala combination but I have noticed > the doc in Java say for example getContext() vs Scala context(), in my > project I'm using context(), self(), sender() just like you would do in Scala > and it just works. > Why bother maintaining a Java API that is most likely to be outdated or miss > something the next day? > Even from the documentation point of view, it makes things more difficult to > understand and slower to document. > > I'm not saying to remove the ability to use Akka from Java but to force Java > developers to use the same API even if it is Java convention breaking. > There is no point and not even in the Java world we appreciate to be so tied > up with get... prefix so why bother? > > The last and probably the most important question here: If you eliminate the > Java API that is designed to be Java's convention friendly, would Akka miss > any functionality for Java developers? > Maybe at the beginning from an acceptance point of view you wanted to be > Java's friendly, guess what, it is more annoying to try to follow an obsolete > convention than forcing us to evolve and move forward. > > Maybe this is deeper than just Akka but Scala in general if it becomes more > Java 8 friendly and for example pass a Java 8 lambda expression to a Scala > method expecting a Scala trait -or whatever is called- > I don't really know which is why I would like to know your opinion about this. > -- > >>>>>>>>>> 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. -- >>>>>>>>>> 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.
