Since you're not a language implementer what you can do without is irrelevant here.
Re:What the JVM needs
by bnoordhuis on Friday July 30, 2010 @02:54PM
(#1562173)
Okay, then let me tell you what I /can't/ do without. To name a few:
hot-swappable classes
design by contract
re-ified generics
closures
These are all things that have been on developer wishlists for years. Design by contract is the #1 upvoted RFE in SUN's issue tracker, the others are all in the top 20.But what happens? The guys that can make a difference come together and wank about performance hacks for dynamic languages. The 2% of the user base that actually uses Scala and Clojure will thank you for it, but the other 98% is left out in the cold.
Re:What the JVM needs
by inferno0069 on Friday July 30, 2010 @12:27PM
(#1561656)
These features would be most necessary for JVM languages other than Java: Scala, Clojure, etc.
Structs / value types? Nice to have but you can make do with java.nio.ByteBuffer.
Concurrent PermGen sweeping? I work on a big enterprise project like the article mentions but this has never been an issue in production, only development and then only when reloading lots and lots of classes.
Unsigned equality checks would be nice but you can work around that, too.