Is JAVA Relevant Anymore?
I ask this question not because I am trying to surf for responses. I’m actually more interested if JAVA is relevant to our readers. There are so many tools and languages it is difficult to keep on top of them. I find I more often than not miss on a great new library or framework simply because I don’t have time or a project that lends itself to discovering new techniques.
Take web services on the Microsoft platform. How many ways are there for creating and hosting a web service in the last 5 years. At least three. That is a lot to keep up on and be proficient.
So, yesterday I mentioned the fact that many of the open systems projects purchased by Oracle from SUN Microsystems have been forked and taken into new open systems projects, abandoning, or at least not being tied back to the original ancestor. I’m thinking JAVA should do the same.
The point is, we used to compare Dot Net to JAVA for the things that were missing. Today the question has reversed where we compare JAVA to Dot Net for the things that are missing.
There is still the advantage the JAVA runtime engine has over Dot Net in that it is less platform dependent. Dot Net may run on other operating systems, but the support of the Framework lags behind the specifications, except on Windows. JAVA, in contrasts, tends to be fairly consistent across operating systems.
So, is it time to resurrect JAVA and pick up the pace? Or, is it time instead to work on producing run time engines allowing us to utilize the more full feature libraries of Dot Net outside of the Windows Operating System? Are there other completely different avenues we should consider, ie. Google?
Share your thoughts and get into the discussion by leaving your comment below. Tell us if the question of JAVA or non-windows operating systems is even on your radar. Share your thoughts about how we should move forward as a community. You can even drop an email to btaylor@sswug.org if you don’t wish to leave your thoughts online.
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
The LINQ to SQL Data Model – Part 1
LINQ to SQL is a technology that allows you to create an object relational mapping between the tables in your relational database to objects. You can imagine LINQ to SQL as an object mapping tool that makes easier for developers to develop data centric applications using Microsoft SQL Server. It basically allows having a one-to-one mapping to the tables in a relational database. LINQ to SQL internally represents the relational structure of data into object representation. Using LINQ to SQL you can perform all sorts of operations that you do in a real time data centric application. Queries are represented using LINQ queries which are then converted into T-SQL statements and executed by the data source.
Featured White Paper(s)
Encryption Key Management Simplified
Managing encryption keys is a fundamental step to securing encrypted data, meeting compliance requirements, and preventing da… (read more)
Featured Script
dba3_DataLength_And_TableColumnWidth_Demo
considerations when using DataLength (), Information_Schema.Columns and special system stored procedures that return informa… (read more)