|
I appreciate fear of churn, but Java as it stands today isn't vaguely as good for writing reliable code as it could be. Maybe it is time for another language, but I don't like any of the current JVM languages enough yet. And tooling support is still best for Java. That's the predicament that I think a lot of us face. If tools only exist (in good enough form) for Java, but Java otherwise has lots of warts and trouble, what to do? But churn in the language also stirs things up. |
java.net RSS Feeds
