Yes, if you're willing to pay money you'll get support or even bug fixes (assuming that Sun is still around in the year 2018, or even just 2013), but otherwise there will be no help and no further releases.
Ping & DNS - updated with new look and Ping home screen widget
doesn't matter 1.4, 1.5, 1.6... the basic java or OO design hasn't change dramatically. what you learn here is something you would never ever learn from other computer/programming courses. It's like XP programming (extreme programming), you can benefit from looking at each other's code. Even better, they guide you how to write better code here in cattle drive.
I've probably said this before... but in my day job I don't write any Java at all. What I've learned here has been invaluable in the other languages I work in.
It also put me on the trail to read things by Martin Fowler and Robert Martin and Mike Cohn and countless others who challenge the way I think about things every day of the week.
Joined: Mar 22, 2005
since Java is now open-source, if Sun went out of business, I suppose that somebody would support Java 1.4 and 5.0 etc.
There would probably be a follow-up company, but all versions before Java 6 are not open source, and will not be, because they contain proprietary 3rd party code to which Sun does not have source code rights.
I have to second Katrina, I am a "mainframe guy" and even worse more on the systems side than application development. Everything I have learned here so far is great, my biggest issue all along has been style. I
tend to cobble and provide "emergency solutions" outside of any change control environments at work.
Techniques learned here can be applied to other programming languages, even cobol and rpg now have
free form, hardley a difference other than built in functions.
As a code vigilante I submit to Java Ranch mainly to practice breaking many years of terrible habits and learn "a"
right way to do things. Doesn't really matter to me what language or version, good habits will follow wherever you
go. Here is a question, does the code learned here compile in 1.6? If so, and though it might not be taking advantage
of the latest enhancements, finding out there is an easier way is always better for me than not being able to
do it at all. Code written for a specific release is almost never backwards compatible, but can usually be ported forward.