Gosling: What's Good for Google May Not Be Good for Java - The Java Innovation Leaders (
Page 2 of 3 )
Q: Where's the innovation going on in Java today?
A: It's all over the place inside Sun. People are doing cool things in any
direction you want to look. The enterprise guys—the GlassFish group—they're
totally on a tear these days. The OpenDS guys are being really successful. The
OpenJDK guys are getting some real traction. Stuff like the Jigsaw modularity
stuff is getting a lot of excitement.
Q: Is that [Jigsaw] complementary to OSGi or different?
A: I think it's kind of both. OSGi is this thing that kind of came from a
different universe that's being used for modularity. And it's kind of huge and
a bit of overkill. So we needed something that was a lot lighter weight.
Q: So it would have the same functionality as OSGi?
A: Yeah. But with none of the other stuff that was irrelevant.
Q: Well, I know Eclipse is big on OSGi, and a bunch of the enterprise
Java players are pushing it.
A: And we even use it. But it doesn't play well in the smaller spaces. I
guess it's just too overwhelming. If you start worrying about modularity in
some of these other interesting places and you're like, OSGi's just too much
fat.
Q: Where are we with the issue of what language comes next? People say
the JVM [Java Virtual Machine] supports all of these languages and one of them
is going to supersede Java at some point.
A: Maybe. I actually would like to think so. It would be weird that, for
what life span human civilization has, Java stays in place and nobody comes up
with something that takes over. That would be just wrong. But the important
thing isn't really Java the language, it's the JVM—the integration hub. And the
fact that we can have all kinds of languages that get along together. You can
be writing JRuby code interacting with Scala code with great performance, and
it works really, really smoothly. The JVM is the piece that actually matters.
Q: So are you more accepting of dynamic languages these days?
A: Well, I don't know whether "accepting" is the right word. At
the right times and in the right places, I think they're great. If it's not too
much of a performance penalty. Because most of them have made design decisions
that cause them to be way too slow for the things that I normally do.
Application Development News & Reviews 
