3 ms·
Java needs feature opt-in, import future.sane.Generics; and so on. (Scala has these.) Python learned it the hard way. The value of backward compatibility got a
by pas 13y ago
Java needs feature opt-in, import future.sane.Generics; and so on. (Scala has these.)
Python learned it the hard way. The value of backward compatibility got a bit underestimated there, with Java it's going the other way (the value of progressing, giving better tools to developers is overlooked). The JVM is a big bag of crazy code already (HotSpot with C1 and C2 JIT compilers, the many garbage collector algorithms/implementations and the other stuff that is currently deemed the JVM's responsibility), so there's plenty of space for new opt-in features.
- mcosta 13y agoFeature opt-in sounds good. The C++ people did it. Look what happened. Qt, boost, gtkmm, mscf are all (more or less) good. But you can't (shouldn't) mix them.
- nly 13y ago> Qt, boost, gtkmm, mscf are all (more or less) good. But you can't (shouldn't) mix them. I think you're missing the point of generic programming.