2007 Java Predictions
jg21 writes "Java Developer's Journal has published the results of its end-of-year poll of various Internet technology players, from its own internal editors to industry high-ups like the founder of Apress, Gary Cornell, and including too the thoughts of professor Tony Wasserman of Carnegie Mellon West. Participants were asked to foretell what they saw happening in 2007. Among the predictions — Cornell: 'The open-sourcing of Java will have no effect whatsoever on Java's slow decline in favor of dynamic languages (Ruby, Python) and C#'; Wasserman: 'The use of the GPL 2 for open-sourcing Java will inhibit the completion and acceptance of the GPL 3 proposal'; and Rails creator David Heinemeier Hansson: 'The stigma of being a Web programmer still using Windows will increase.'"
I read this on a messageboard years ago, it still makes me laugh to this day:
No one uses Java anymore, it's all flash these days.
Summation 2
Attaching a stigma to certain platforms or technologies for certain jobs is just stupid and childish. Are we going to start lambasting publishers that don't use Macs next, or Linux users that do accounting on their machines? Bizarre...
Hansson's prediction was that Apple will become the development platform of choice for techies and, consequently, other developers will laugh at any web devs saddled with using a Windows based laptop.
Is is an ivory tower troll. In fact almost no one uses ruby. It may be hot among Nerds and its growing. Java went into the enterprises in the 90th as Cobol did before. C++ was less usable for enterprises. Java looked good and fostered plattform independency, helped to increase interoperability. "Java to go" is as off-topic as the prediction that FreeBSD would take over Linux. Ruby and Python are upcoming languages. Growing but you have to wait for another five years. Open Source Java will mean all Linux systems will ship free Java. Java will get a working GNU compiler native compilation. Java will be the trusted alternative to -- arrrgh patents --- Mono for enterprise applications. SUN knew exactly why they did it. Linux will become a strong Java plattform and with Linux on so many servers that will give Java and Linux a boost.
Didn't have you coffee yet this morning?
The parent makes a living programming J2EE. He might even use Eclipse.
I think for many folks Java is used to write software that does not see the front of a web page.
In fact I have not used Java on the client side since about '98. But I write far more Java now than I did back then. I hope that the work Ethan Nicholas is doing to will help, but frankly Flash works fine for many web pages. And as long as I don't have to write the Flash code I'm fine with that. Is it still programming via dialog box? Can I use svn with my Flash code these days? I also hear AJAX is popular and effective for client side work. Anyway, Java is not likely to die anytime soon.
In no particular order:
Java as Open Source will help in creating smaller versions - perhaps very lightweight browser-plugins - optimized for particular use (media, number crunching, etc.). These browser plugins will help revive Java as a thin-client/web2.0 (3.0?) player in browser-based apps, possibly even making some small inroads against Flash. The 'apollo' project from Adobe may put the kibosh on this, but the increased-eyeballs angle will likely prevent a complete obliteration from happening to desktop Java.
Java will become even faster. Although this has happened in 2006, with the release of Java 6, the full impact will be a refitting of the niche Java apps out there to work specifically with Java 6 and the speed improvements there. This will give some Java some good PR points and case studies with the 'Java is slow' crowd (which I'm definately a member of).
(As I think one of the panelists in the article said) - there will be a greater acceptance of dynamic languages (ruby/php/python/etc) in Java shops, as Java6's support for dynamic languages (JSR 223 I think) will help increase productivity for Java devs willing to think outside their javaBox.
creation science book
Did anyone really expect JAVA to be released as GPL v3? A license that hasn't even been written yet? Or wait until GPL v3 is released (is there a set date for that?)?
Help! I'm a slashdot refugee.
My parents recently bought a new HP computer that came with the SUN JRE preinstalled.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
I am personally really excited about Java becoming free. I quit using it a few years ago because of Stallman's The Java Trap (that and the dark side of easy unmaintainable web development in PHP drew me in... stupid me). I'm currently reevaluating Java right now and Python is really shaping up for the server side too. But back to the point, people forget that there is a MASSIVE collection of libraries out there for Java. And I mean massive. Check apache.org just for a little taste.
Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
AJAX is dying. AJAX will grow. AJAX has no future. AJAX has a future.
JAVA is irrelevent. JAVA will grow.
Apple is irrelevent. Apple is irrelevent...oh, they agreed.
Anyway, anyone who takes these kind of articles seriously are wasting their time. Our shop does IIS, ASP.NET, SQL2005, Ruby-on-Rails, MySQL, VB.NET, C#, C++, Borland, MS, and Linux OSS flavors. In other words, we have the tools and the skills to do what is necessary to get the job done, the way our CUSTOMER needs it to be done. No tech prima-dona BS of telling the customer that we won't give them what they want. If the customer doesn't have implementation requirements, then we determine what they need, suggest and then build on their approval.
Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
The problem with Java has only in part been the license; mostly, it has been Sun's stifling control over the platform
You mean like preventing MSFT from writing their own incomptable version? How long have you been following java for? What exactly has Sun been stifling? Name a couple of things.
As a result, Java has numerous technical problems.
Such as?
You don't have to buy the all-show no-go over-priced Apple hardware.
Blar.
Oh please, use what's right for your environment. And frankly in the web space what's on the back end shouldn't matter one bit, it all pumps out HTML/XHTML/RSS/whatever. Unless of course he's saying that Ruby just sucks on Windows; in which case whose fault is that really?
Using an IDE no matter if one is a rockstar or an average programmer is going to make work go quicker. There's more than enough things to think about on any given project and and IDE just lets one focus better on the more interesting parts of the project instead of things like repetitively typing import statements.
Java is great for writing business rules and the back end and for industrial enterprise level scalable code.
Other things are better for the front end these days. No big deal.
Front ends change a lot. Business rules tend to be stable. Do you really want to redevelop all your business rule every 3 to 5 years? With java, you write it once and for the foreseeable future don't have to rewrite it. But java is a bit heavy for fast moving stuff.
She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
The entire IT reporting industry, and Slashdot. Writes about languages these days as if there is only one task in the world: web apps whereby users insert and retrieve basic data to/from a database. Yeah, for those apps you bet Java is losing ground to modern interpreted languages.
But there are a thousand other types of projects for which other environments might excel.
One of my current projects is a desktop app that does real-time signal processing on a live microphone feed, and produces a full-screen GUI with output of the signal that updates at 30+ FPS. Between the signal processing and graphics, it needs to do some hundreds of megaflops, effective - interpreted languages are a couple of orders of magnitude slower doing raw math. Java is pushing the low end of speed for this app.
At the same time, we want the benefit of a multiplatform release, because the project is for the education and music professional markets - there are an awful lot of macs among our target market, and our competitors are PC-only. Java has actually come through on the write-once-run-anywhere promise for us, straight down to the live audio input. We're just 2 developers - how much longer would it have taken us to have to port C++ between different platforms' APIs? Way too long. And we can't even consider platform-specific environments like C# or ObjectiveC/Cocoa.
Use the right tool for the right job. There are times when Ruby's the right tool - and times when it ain't. There are plenty of niches still where nothing else can remotely fill Java's shoes.
I stole this sig from someone cleverer than me.
Cornell: 'The open-sourcing of Java will have no effect whatsoever on Java's slow decline in favor of dynamic languages (Ruby, Python) and C#';
In 2007, apples still won't be oranges.