Fatal Exception's Neil McAllister writes about what could be the end of the Java Community Process as we know it. With the Apache Software Foundation declaring war on Oracle over Java, the next likely step would be a vote of no confidence in the JCP, which, if the ASF can convince enough members to follow suit, "could effectively unravel the Java community as a whole", McAllister writes, with educators, academics, and researchers having little incentive to remain loyal to an Oracle-controlled platform. "Independent developers could face the toughest decisions of all. Even if the JCP dissolves, many developers will be left with few alternatives", with .Net offering little advantage, and Perl, Python, and Ruby unable to match Java's performance. The dark horse? Google Go - a language Google might just fast-track in light of its patent suit with Oracle over Android.

Yes, the Go language is one of them, but there are others. What about D? It has the speed of C and the power and simplicity of Python or Ruby. There are even public domain OSs written in D - https://github.com/xomboverlord/xomb-bare-bones

The news in itself I think does not say that will not destroy Java as it is. JCP is just a small part. Even resilient to die products (COBOL or Fortran) were replaced at one degree to more mainstream languages, it does not mean that a missing standardization process will do break Java apart.
Also, I really think that Go is not a replacement for Java. Go is a different paradigm. I never heard a game written with it, or a browser of that matter. The part that I really think that Go will replace, will be on lightweight servers. Go also have no tooling to replace Java on rich client and enterprise. Language wise, is also a different beast. So about Go, I think it has a long way to go

Yeah, me neither. For whatever benefits it has for the developers, it sucks for end users. It sucks on the desktop... people say it's possible to write fast Java apps with a native look and feel, but considering how few developers have managed to pull it off, I figure it must be harder than it needs to be.

I don't know much about it on the server, except that where I work, I'm constantly having to restart Java server apps (that I did not write) for out of memory errors, processes getting stuck, manhandling system resources, etc.

I've been a Linux user since the mid-90's. I've watched Java go from a closed-source project to an open one, and now, apparently, partially headed back to closed. I think we will see Java stick around for the Enterprise world, which has mega-bucks invested in fat J2EE apps. But the "buzz" in the rest of the market is cooling quickly. A language loses it mindshare first, then the rest slowly follows. Unless Oracle has a major change of heart (hah!), it's on it's way out.

is there anything wrong with old? C++ still does a good job, as does Ada. Whatever language is hip in 30 years will probably live a longer life than Java, I mean if the "build upon the past" principle applies of course.

Also, I don't understand how clumsy Java is... do you refer to the verbosity of its syntax? If so, from my point of view, Java is cleaner than C++ without a doubt.

As long as there are JEE containers available, the JEE web solutions are here to stay. Java Web stack is pretty steep and powerful and the codefactories continue to push out java-based web solutions. Nobody cares if java is open or not as long as it produces income to finance the business.

Nobody cares if java is open or not as long as it produces income to finance the business.

Maybe but it doesn't mean people shouldn't care. Tomcat is huge in JEE even if it's not necessarily the production container. JBoss and Glassfish are Tomcat-based/-derived and all developers I've ever met (granted they aren't that many of them and I'm probably not "typical" enough for drawing statistical conclusions) used Tomcat. And Apache is even bigger! Of course, the ASF won't stop producing Java code but there's been a clear trend since Oracle owns Java that should make people care even though a sustained flow of money is flooding in.
As I said in another comment, when Eclipse and Apache people talk about JEE, I do listen. Even Oracle should care.

Well, I've been researching various fields for a few months now, in order to build an open desktop software platform for things related to music score editing. I had already made my mind about several architectural choices. Java is the language I chose despite it being already almost non-existent on the desktop: the only Java application I ever used as a desktop user is Limewire. All the rest is professional (Eclipse and other IDEs, Jetty, Tomcat, and all the Apache libs - Commons first- and tools like Maven).

Non-existent on the desktop but with very nice functionalities/features/possibilities like SWT or OSGi (the only problem I still have is to decide whether to choose Eclipse Equinox or Apache Felix as osgi platform).

I can only get confused when I read that the Eclipse Foundation and ASF are both worried. These are two big players as none of my work days in the past years has gone by without involving something produced by or related to them (unfortunately, this includes the excruciating Lotus Notes... that's the magic of open source). Even individual big names like Stephen Colebourne seem wary of Oracle's moves. I knew I knew this guy's name, probably saw it in some javadoc, but I had to do some googling to realize why his name sounded familiar.

I'm wondering if I should also start worrying and investigate Qt+C++. Should developers start worrying?

Oracle bought Sun "because of" Java, Ellison had already said Java is the biggest asset. People should have listened to the statement with a businessman's ears. Then, the "premium Java for enterprise customers" would have come as no surprise. Whatever features that premium version contains, I guess there'll be some language syntax changes to accommodate those features. Then what becomes of the "write once, run everywhere" motto? Ironically, the same people are suing Google for (what I interpret as) making that very motto stale...