There's a darn good article online against using Java for enterprise development but like so many others it fails to point toward a viable alternative, "Clear standard alternatives to Java and C# for custom-developed applications do not exist."
Reasons cited for wanting to get out of 'Java town' include:
- a) There have been zero-day type events in the past where you needed to upgrade Java immediately or risk having your machine turned into some kind of bot
- b) The presentation layer tools can be a pain to use (Swing, et.al)
- c) Heavy reliance upon frameworks (increases the learning curve and contributes to application bloat)
- d) Based on C++ syntax which isn't gobs of fun to work with in the first place
- e) Oracle bought Sun and inherited Java but there's always been trepidation that they would treat it like an unwanted step-child
In Gualtieri's article we get a fuzzy answer about what tools could be used to supplant Java when the article was written (Q4 2010). C# was discounted quickly: "C# is not the alternative. It is little more than Java Microsoft style." Ouch. C# shares a lot of the same problems Java has mainly due to it having similar beginnings.
As of July this year the number one language was still Java (if you only look at job postings). Other publications like eWeek agree that Java has more developers, more projects and much more 'oomph' in the marketplace.
Nevertheless Java suffers under Oracle's leadership with the Apache Foundation resigning from the Java SE/EE Executive Committee late in 2010 due to licensing concerns. At present Google searches for 'Java alternative' or 'java fork' reveal very little so it is safe to say that although there have been problems with Oracle's handling of the Java language there is no large-scale project to build a fully open-source alternative. Furthermore, the Apache Foundation maintains a huge number of Java-based projects, supporting the idea that Java is here to stay despite bugs, shortcomings, and unhappiness with the new ownership.
All this points toward giving Java a break when it comes to DIY LIMS development. You could do a lot worse and try to write your LIMS DIY project in C but then you would inherit all of the headaches porting to different hardware platforms that a language like Java was meant to save you from in the first place.Go Back
Citation: Cut Java a Break or Cut it Out. (2013). Retrieved Wed Mar 22 22:12:21 2017, from http://www.limsexpert.com/cgi-bin/bixchange/bixchange.cgi?pom=limsexpert3;iid=readMore;go=1374512902