On Thu, Jul 19, 2012 at 5:58 PM, Kevin Wright <[email protected]> wrote: > Case in point... Sun/Oracle took too long to add modules so they could > remove deprecated code from Java, they've been suffering from postponed or > feature-limited releases as a result.
I question how much they are "suffering" from this. There is a vocal minority that wants it, to be sure. The industry, by and large, seems to not care. > Once you have modules, it becomes far easier to release everything else in a > perfectly useable but less than 100% complete condition, because you then > have the scope to revert design choices in a subsequent version. This really only works if you don't have entire industries that depend on your current design remaining. Pollack's critique of Scala's system for being ridiculously fragile would be a pale candle compared to the flame that you seem to be describing. http://lift.la/scalas-version-fragility-make-the-enterprise -- 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.
