The only reasonable, although political, explanation I see why they would prefer crippling Option on purpose is that they want to prevent a huge, general paradigm shift from using nulls to Option. This change would certainly be much more disruptive than the introduction of Generics.
The response on the lambda mailing list reminds me of that response from the Guava guy which was also along the lines of "don't even bother talking to us, everything you could say was already considered and rejected internally". In contrast, I remember an improvement request against Option (concerning a "forgotten") where reporting, acknowledgement, patch creation and pull request happened in *4 hours*... I guess that we are experiencing the difference between "open source code" and "open source development" right now. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/9dOmvyYp8FkJ. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
