I am experienced J2EE and JEE5 developer and my career is secure with JAVA. but now I hear from every body that .net took the market and java is a new COBOL. This mean java stay but new development is gone with .NET. This is true up to some extend that small and medium business get attract from .NET.
I like to ask the SUN team and the community that why we stick with JAVA 2 and why not sun release JAVA 3.
They can redesign the whole JVM from the scratch. Like Microsoft learn from JAVA and come up with .net we can learn from .net and JAVA to redesign JAVA and omit all the depreciated API.
SUN and JAVA support backward compatibility for more than 10 year. Now its time to break it for ruling the next 10 year and it is not bad.
About the legacy code we can make a bridge. Like if some body want to run jdk 1.4 code with JAVA3. He can install 2 jdk. j2sdk and j3sdk. but for new development 1 can start with JAVA3.
Same in the enterprise development we should have J3EE that work with new API and spec and framework. If some body need to use EJB2.1 he can install 2 server J2EE and J3EE and there is some way for communication.
I have all these ideas and Question in my mind and I like to check the response of java community.
I am experienced J2EE and JEE5 developer and my career is secure with JAVA. but now I hear from every body that .net took the market and java is a new COBOL.
As far as I can tell, that's absolutely nonsense.
But even if it where true, there wouldn't be much to fear - C# is so close to Java that a switch wouldn't be hard at all.
What's much more interesting is the trend to dynamically typed languages like Ruby, Groovy etc. I think we can expect more there in the future.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus