Google confirms next Android won’t implement Oracle's proprietary Java APIs

Re:Google confirms next Android won’t implement Oracle's pro... by kuschku on Tuesday December 29, 2015 @06:19PM (#10809713)

You wanna know what I did?

    1. Use RetroLambda
    2. Write your own implementation of Streams and Optionals, compatible with RxJava and Guava
    3. Use in your project
    4. Profit

[ Parent | on HN ]

Re:Google confirms next Android won’t implement Oracle's pro... by benwilber0 on Tuesday December 29, 2015 @06:28PM (#10809761)

well that doesn't really scale at all though

[ Parent | on HN ]

Re:Google confirms next Android won’t implement Oracle's pro... by saurik on Wednesday December 30, 2015 @02:30PM (#10813816)

Ok, in what way does it not "scale"?

[ Parent | on HN ]

Re:Google confirms next Android won’t implement Oracle's pro... by jayd16 on Wednesday December 30, 2015 @03:02PM (#10814000)

I do this, you do this. We try to use each other's code. Now there's two competing implementations that are probably incompatible.

[ Parent | on HN ]

Re:Google confirms next Android won’t implement Oracle's pro... by s73v3r on Tuesday December 29, 2015 @06:35PM (#10809796)

No one should expect everyone to do that. This is basic, platform level stuff, that Google should be providing, unless they want Android to stagnate and whither away.

[ Parent | on HN ]

Re:Google confirms next Android won’t implement Oracle's pro... by kuschku on Tuesday December 29, 2015 @10:21PM (#10810501)

Obviously. But by now most have accepted that Google is just unable to provide any reasonable solution to this, and built their own libraries.

Often (ButterKnife, NineOldAndroids, etc) even better than what Google themselves provide.

[ Parent | on HN ]