Giovani Salvador's Blog: Community Archives

I was trying to think specifically when a developer, who codes in a specific programming language, is starting to become a dinosaur. It's not his/her age because there are lots of old guys working with new technologies and even creating them.
But when I was reading this post from Bruce Eckel (it has been discussed here as well) I was thinking that when a technology stops doing new things then that technology is in process to make its "followers" as dinosaurs. Of course, Bruce Eckel is not fully suggesting Java should stop adding any feature. His point relates for adding features when we really need them.

But if Java starts the process of becoming, as he says, "stable" then does that mean we are becoming dinosaurs?

Let's analyze some things:

When a programming language stops adding support to new technologies then how that technology will have new people working with it? Imagine if Java has not provided any answer on SOA (through JBI or Web Services)!? Nowadays is all about SOA. But how would developers make their applications "SOAble" if they could not find in the language they are using a support for that feature? They would migrate to new programming languages or technologies that can offer such approach.
Would the same developers create applications in that "old" language even if language support all the application's features? I don't think so. How many C/C++ applications are being created compared to technologies like Java and .Net?
I don't have the answer but at least in the world I live I don't see that much (I would like to say none at all!!!).

Another interesting thing is that today in JCP, the number of JSRs in Review Stage is 0 and there is only one Early Draft Review.

If Java (JCP) starts the process of reducing the number of new features added to the language (or being "stable") then I really believe I am in the beginning of the process of becoming a Java dinosaur.

Powered by
Movable Type 3.01D

java.net RSS Feeds