Top 10 Java Lies

By Angsuman Chakraborty, Gaea News Network
Monday, March 6, 2006

Here are the top ten Java lies I have heard over the years. Feel free to add yours in the comments. Enjoy!

  1. Java is slow
  2. Java is dying / dead
  3. Java is not free
  4. Java sources are not available / documented
  5. J2EE is required for enterprise development
  6. Applets are unusable / slow / dead
  7. To learn Java learn Ruby / C.
  8. Java is hard to learn.
  9. C / C++ / PHP (take your pick) is the leading language, Java is far behind
  10. The programmers you’ll be able to hire to work on a Java project won’t be as smart as the ones you could get to work on a project written in Python” by noted Java hater (BTW: He has “never used” Java so he probably thinks he is the best person to critique it.)
Discussion
January 28, 2010: 12:54 am

information about java

October 25, 2007: 4:10 am

Hi there,

i want to specify another java lie that;

Java programmer wants more money so the java projects needs more money and more time for finding java programmer.

March 7, 2006: 8:51 pm

@Joost
I use 1.8Ghz as well as a 400Mhz machine with jdk1.5. I have never felt startup time as an issue, deefinitely way under 3 seconds. Try running a HelloWorld to verify my claim.

Multi-process JVM is also a solution as Avid said before. However with the startup times I am seeing I fail to see why it is an issue.

March 7, 2006: 3:27 pm

[...] So here it is the Top 50 list of TopWhatever lists out there 10 improvement goals for the less-than-perfect end user The Top 10 People Who Should Be Podcasting Top 10 Geek Watches Top Ten Reasons to Go Into Space Top 20 Extinction Hotspots Top 10 java lies Top 200 Constructed Languages of 2005 Top 10 Tips For New Eclipse Users Top 10 Parent Fears The Top Ten WordPress Plugins Top 10 Antispyware Apps Top 10 Accidental Discoveries Top 10 Strangest Lego Creations Tendango Top Ten Lists Top 100 most popular Laptops Web 2.0 Directory : Top Web 2.0 Sites: 900+ Top Windows tweaks Top 10 Ways to Find Great Photos on Flickr Japan Votes on All Time Top 100 Videogames Top Ten Felons in Pro Sports 7 Top Tax tips for students Top 10 Terms Searched on eBay includes term “Yahoo.com” Technorati Top 100 Most Popular Blogs Top 100 of 2006 - Open Source Mania Top five tips for understanding virtualization The Top 10 Video Game Weapons!! The top 10 most popular Open Source Website Templates [ Photos included ] Top Five List - Alternate Uses for iTunes Star Rating System top 8 firefox extensions for web developers Top 10 peeves of a support tech Top 100 ranked restaurants in Fast Casual Top 10 Keyboard Shortcuts in OS X The Top 10 People Who Should Be Podcasting Current Top 15 Internet Searches (always up to date) New List: Top 20 Extinction Hotspots Top 5 JavaScript Mistakes Tuesday’s Top Ten: Top 10 signs you spend to much time online Top 100 intellectuals Top 10 Blogs Top 10 Strangest iPod Accessories Top 10 Things I Will Miss About My Blackberry If They Shut It Down The Top 10 Reasons To Switch To Linux Top 10 Web 2.0 Mashups Top 10 Tuesday: Worst Game Controllers Top 10 Signs Your IT Department’s Budget is Too Low Top 48 improvements Google should make to Gmail Top 10 Disposable Email Address Services Top 5 fastest growing countries on the Internet Top 10 Strangest MP3 Players Home Business, Top 100 Home Business Opportunities, Work At Home…   Add to: document.write(”Del.icio.us”) | Digg it | RawSugar | Slashdot | Y! MyWeb [...]

March 7, 2006: 10:04 am

Joost: They’re working on that issue… Something called the multi-process JVM…


Joost
March 7, 2006: 2:41 am

I do think Java insulates you from the computer and as such is a bad place to start learning. If you can do C/C++ you can do Java, but not the other way around.

And I think the JVM loading time is a huge issue; you might get away with ignoring it for long-running programs but certainly not for short-lived programs. More than 3 seconds of waiting before anything happens is too much to ask of a user, it interrupts their flow.

March 7, 2006: 12:10 am

When the whole dotNet started coming out (but Really coming out, not just DNA and some predated stuff) the C# developers kept running on a rumour that Java is interpreted and thus will always be slower than dotNet, which has a JIT compiler. Even though it was a Java lie, it was during 2000, so JIT wasn’t that old in Java.

Unfortunately, I heard the same rumour even last year!

YOUR VIEW POINT
NAME : (REQUIRED)
MAIL : (REQUIRED)
will not be displayed
WEBSITE : (OPTIONAL)
YOUR
COMMENT :