|Re: [ee4j-community] Eclipse Jetty and EE4J|
I think that example is indeed not pretty, but actually argues for why RIs facilitate lazy specifications. If the process required several implementors to implement the draft and do interop testing before going final, than such poor specifications would be noticed earlier, without making one implementors version the defacto standard regardless of merit.Note also that most implementations continue to be developed after the specification is pronounced final, and who is to say that an RIs subsequent development direction actually expresses the intent of the expert group? If difficult problems are subsequently discovered, surely they should be taken back to the expert group for resolution rather than be left in the hands of one specially anointed implementation?
Back to the top