Hopefully the last message on Block

[Kevin Bourrillion]

Fabulous. Good-bye, Block. We thank you for your term of service.


On Fri, Jan 25, 2013 at 8:44 AM, Brian Goetz <brian.goetz at oracle.com> wrote:

> The poll results are in:
>
>
> https://www.surveymonkey.com/**sr.aspx?sm=7JZdXUDIBZ6bFD_**2bCY7jEghy5Rv_*
> *2b7iObJtf9AUFPp63k_3d<https://www.surveymonkey.com/sr.aspx?sm=7JZdXUDIBZ6bFD_2bCY7jEghy5Rv_2b7iObJtf9AUFPp63k_3d>
>
> My interpretation of the results:
>
> Supplier / Block (the status quo): OK, people clearly don't like it.
>
> Supplier / Sink (change Block to Sink): Better than above -- more like,
> less hate -- but not overwhelming support.  Clearly dominates #1.
>
> Supplier / Consumer (change Block to Consumer): Strong support, little
> hate.  Clearly dominates #1 and #2.
>
> Source / Sink: Strong support (arguably the strongest, but see below.)
>
> Producer / Consumer: Comparable to Supplier / Consumer, but with some
> caveats.
>
>
> Any of the last three choices would be supported by the data.  It was
> commented that Source/Supplier is better than Producer because Producer
> more strongly implies a *new* item is being produced (same reason we
> switched Factory -> Supplier.)  I think this is a strong enough argument to
> remove it from the group of supportable candidates.
>
> Source/Sink had more votes, but if you remove the Oracle votes (of which
> there were a lot), its pretty clear that this distorted the results. (Use
> Crosstab to filter the results by Collector; the Oracle folks all used the
> web collector because our mail system seems to filter out the surveys.)
>
> So I think the strongest choice is Supplier / Consumer (simply renaming
> Block to Consumer.)  People like Supplier already, and seem to be able to
> deal with Consumer.
>
> If you've got extra paint left, there will be more bikesheds coming, don't
> worry.
>
>


-- 
Kevin Bourrillion | Java Librarian | Google, Inc. | kevinb at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20130125/6c59c274/attachment.html