Java may not be dying, but it does take off early on Fridays for golf. Java is not dying the same way Cobol was not dying 10 years ago. It has a lot of legs left but nobody is 'hoping' to use it, they are told to do so. Java is and always has been almost completely a corporate tool. Again, like Cobol, so the 'cool kids' are not going to give it much love. It's too slow to execute to compete with C++, its too slow to…
I'm fairly certain Java and C++ have comparable speeds, and I think in someways Java's faster.
If Java Is Dying, It Sure Looks Awfully Healthy
41–50 of 327 posts
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#42Java may not be dying, but it does take off early on Fridays for golf. Java is not dying the same way Cobol was not dying 10 years ago. It has a lot of legs left but nobody is 'hoping' to use it, they are told to do so. Java is and always has been almost completely a corporate tool. Again, like Cobol, so the 'cool kids' are not going to give it much love. It's too slow to execute to compete with C++, its too slow to…
I'm fairly certain Java and C++ have comparable speeds, and I think in someways Java's faster.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#43It's funny the article straight away brings up the verbosity argument as well. You want to talk about verbosity - take a look at Objective-C and Cocoa (again, hugely popular today!)!
Personally, I quite like Java.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#44Java may not be dying, but it does take off early on Fridays for golf. Java is not dying the same way Cobol was not dying 10 years ago. It has a lot of legs left but nobody is 'hoping' to use it, they are told to do so. Java is and always has been almost completely a corporate tool. Again, like Cobol, so the 'cool kids' are not going to give it much love. It's too slow to execute to compete with C++, its too slow to…
I'm fairly certain Java and C++ have comparable speeds, and I think in someways Java's faster.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#45Re: If Java Is Dying, It Sure Looks Awfully Healthy
#46I primarily use java in my day job, and although there's a lot not to like about it, some standard complaints are somewhat overblown. For example, nothing really forces you to use long variable/method names, but even if you do, a modern IDE -- I use IntelliJ -- with auto-completion makes these fairly painless. It's not like you have to type every letter of "SomeClass.veryLongMethodName()" -- rather, you type "SomeCla…
> Similarly, I never type "for (int i = 0; i As someone who didn't realize this existed in Intellij, I think you may have just changed my life :)
Best shortcut that every IntelliJ user should know is "Find Action" (ctrl + shift + a on Win), press and start typing what you want to do. Will even present shortcuts in the list for next time.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#47Java is doing just fine and with the addition of closures in Java 8 I expect the already incredibly rich set of libraries to improve dramatically.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#48I primarily use java in my day job, and although there's a lot not to like about it, some standard complaints are somewhat overblown. For example, nothing really forces you to use long variable/method names, but even if you do, a modern IDE -- I use IntelliJ -- with auto-completion makes these fairly painless. It's not like you have to type every letter of "SomeClass.veryLongMethodName()" -- rather, you type "SomeCla…
> Similarly, I never type "for (int i = 0; i As someone who didn't realize this existed in Intellij, I think you may have just changed my life :)
A couple years later when Eclipse came out I told a coworker this anecdote and he joked that it was 'main' + ctrl-spacebar followed by 'sysout' + ctrl-spacebar. I lol'd.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#49Also,
>When the JVM implementation of Ruby, JRuby, added native support for this instruction, its performance zoomed past the C-based Ruby VM, which for years has been the Ruby reference platform. As JRuby's performance continues to pull ahead, I fully expect it to become the reference implementation. Certainly, it will become the vehicle by which most organization first try out Ruby.
This was true at some time, afaik the MRI Ruby on 1.9.3+ is faster-than or about-the-same-as the equivalent JRuby implementation. I also know zero people who were first exposed to Ruby via JRuby.
JRuby is awesome btw. I just think this article has a bit of a defensive tone...
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#50There's a lot wrong with Java, but even while having moved on and learned / used professionally many other languages I keep coming back to it and its ecosystem. There is still not another language / platform that provides the same level of a variety of things that are important to me: * platform independence * performance * low level features * simplicity and clarity (for reading, writing not so much) * infrastructur…