On 30 Oct 2012, at 15:41, clay wrote:
There are two valid responses: either accept the improvement requests as valid and implement them or demonstrate why they aren't technically superior.
It's more than just a bi-polar scale, Clay. Sometimes it's about API fit and consistency. Not agreeing or disagreeing with your specific assessment here, mind you. Just pointing out that "technically superior" isn't an objective reality, it's a subjective judgment based on a variety of data, including priorities, aesthetic, preference, utility, and subjective qualities such as testability, maintainability, readability (obviousness of client code), etc. That you feel it is technically superior is all well and good - the authors don't agree, and it's not objectively verifiable even if two groups agreed on the priorites… and it's clear that the priorities displayed in this thread don't match those of the JDK authors.
In summary - you could be right, Option/Maybe could be "the shit" - but it still might be wrong for the JDK, or even if right, it is still the prerogative of the authors to have their judgments.
It is also your prerogative to vocally register your disagreement. :D Christian -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
