Objects.firstNonNull

[Patrick Wright]

IMO, another point to add is that there is a proper place in the
developer's toolbox for libraries like Apache Commons* and Guava. The JDK
is by design a bit more low-level and stable, and as long as the APIs are
stable and the APIs offer a platform for expansion, utility libraries can
be built on top of the JDK for ease of use in particular domains. We won't
get rid of these helper libraries, ever, nor should we aim to. They develop
and release at their own pace, and over time can themselves change greatly
while the JDK remains stable.

Patrick


On Wed, Mar 20, 2013 at 8:04 PM, Brian Goetz <brian.goetz at oracle.com> wrote:

> My point was: with 10M Java developers, there are likely to be millions
> of commonly used idioms.  Should we put them all in the JDK?  And if we
> did, could users find any of them?  The bar needs to be higher than
> "I've found it useful."
>
> We're far better off putting our energy into doing things that users
> can't do themselves in two lines, like supporting parallel map-reduce on
> non-thread-safe ArrayList.
>
> On 3/20/2013 2:55 PM, Michael Nascimento wrote:
> > Of course I could, but as in Map.getOrDefault, this is a very much
> > commonly used idiom.
> >
> > Regards,
> > Michael
> >
> > On Wed, Mar 20, 2013 at 3:51 PM, Brian Goetz <brian.goetz at oracle.com>
> wrote:
> >> Or you could write your own in two lines.
> >>
> >>
> >> On 3/20/2013 2:33 PM, Michael Nascimento wrote:
> >>>
> >>> Hi guys,
> >>>
> >>> Since Map.getOrDefault has been added (yes!!!), couldn't a
> >>> Objects.firstNonNull that works like Guava's one:
> >>>
> >>>
> >>>
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/base/Objects.html#firstNonNull(T
> ,
> >>> T)
> >>>
> >>> Then all uses of Objects.firstNonNull would be gone from my code base.
> >>>
> >>> Regards,
> >>> Michael
> >>>
> >>
>
>