I mean we carry stuff around from the days when we (the Java community) felt 'more is good' - you know the days of spit Java Blueprints. > And there is no diff

I mean we carry stuff around from the days when we (the Java community) felt 'more is good' - you know the days of spit Java Blueprints. > And there is no difference in the way Oracle or Sun has managed the JVM Yet coincidentally more positive changes have happened to the language in the last 3 years than the previous 10? I see a language that was dying on it's feet coming back to life - so hence my feelings about Oracle's stewardship (right or wrong!). > And finally again no idea what you mean by countess Java developers wanting to reuse their knowledge but in a different environment. Almost every Java programmer I know and/or meet has their 'other language'. That they use to solve problems that Java has failed in. But a common frustration is the need to relearn a similar but subtly different syntax. Concrete examples are NodeJS (and hence Nashorn, Vert.x et al) for lightweight format neutral APIs. Android for mobile :-) so hat's a win. Go for systems (Python in the past). Objective-C et al Desktop. For me there is no concrete reason why we can't have these in Java (language). But in doing so we need to be willing to throw away components that don't fit. I.e. existing APIs, existing philosophies. Java is much more than the language, however so when tackling problems that aren't large scale serverside applications we need to adapt if we are to reuse. This is an area that I very much am interested in seeing develop. My specific case in hand is Android - which reuses Java skills but has a lot less to do with normal Java programming. Hope that clarifies a bit.