Earlier quoted context omitted.
Many painful minutes spent with slow-like-sloth-taking-a-shit Java desktop software lead me to believe that your statement isn't entirely true.
This usually seems to be due to bad code, or bad GUI libraries (which Java seems to be the king of)
If Java Is Dying, It Sure Looks Awfully Healthy
111–120 of 327 posts
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#112I 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 :)
There's no need for Cmd-J, just write a few characters and press TAB. Try "sout", "psvm", "iter", "itli", and so on.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#113Earlier quoted context omitted.
What language do you think your favorite C compiler is written in? Now compare that C compiler to the jvm compiler, which has the benefit of using detailed information about the exact system configuration and other runtime behaviours during its compilation phases. Which one has the advantage?
C to both of your questions. The JVM compiler compiles for the JVM, which is written in C. So, how again can something written in C perform faster than...something written in C? I'm not claiming that line by line transcription, C will always perform each particular operation faster than Java. But the fact that you could write the entire JVM in C means that you could recreate the exact platform and replicate the resul…
This is absurd.
First of all, there isn't one JVM. There are dozens to chose from, many of them certified. Each implemented in whatever language their designers have chosen.
Some JVMs are meta-circular, meaning they are also written in Java. For example, Squawk, Maxime, Jikes RVM.
Second, even if you mean Oracle's JVM, the embedded version is not the same as the desktop/server one, one uses C the other C++.
Not to mention that after Java 8's release, Hotspot might be replaced by Graal, the new JIT compiler written in Java as well.
Currently being developed and already in use by AMD for their Java/GPGPU work.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#114One of the huge advantages of Java's static typing + somewhat boring/verbose syntax is that it makes writing powerful tools for manipulating Java code far, far easier than any of the C-based languages with preprocessors or any dynamic languages. After working in IntelliJ for a while with its phenomenal refactoring tools going back to any other coding environment feels somewhat stone age in comparison.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#115One of the huge advantages of Java's static typing + somewhat boring/verbose syntax is that it makes writing powerful tools for manipulating Java code far, far easier than any of the C-based languages with preprocessors or any dynamic languages. After working in IntelliJ for a while with its phenomenal refactoring tools going back to any other coding environment feels somewhat stone age in comparison.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#116I'm surprised nobody has mentioned Android yet. When you add in the Android factor, Java is probably still one of the most widely used programming languages today. It'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.
Popular in terms of use, yes, but liked? I don't know, I doubt it. Android and iOS essentially force you to use Java or Objective-C respectively. I don't hate Java, but I don't like it either. It lacks quality of life features that other, similar languages have had for years. I can't stand writing code in it if I don't have to (and don't get me started on Objective-C...) From what I hear from others and read on a wee…
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#117Earlier quoted context omitted.
To be fair, Mono exists, and contains a free implementation of C#.
MSFT could shut down Mono anytime it wants.How many business use mono (to build web apps) in production? Scala,Groovy,Xtend,etc... there is enough languages on the jvm one doesnt have to use any MS related tech.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#118Earlier quoted context omitted.
Automatic memory management...? "Just use Boost" is not a viable strategy when it adds so much complexity in and of itself. I'm not defending Java, but it's helpful to know what the limits of each tool are.
Automatic memory management (especially with a garbage collector) is antithetical to high performance. I like the JVM (for Scala, mostly; Java-the-language can go screw), but there is nothing there really remotely close to C++ and C, and the garbage collector is a very large part of why.. Rust might horn in on C++'s bailiwick, but until then, it's gonna be a while. I strongly disagree that Boost really adds "so much…
Hunting for memory leaks and pointers gone berserk will become someone's full time job.
I like C++, but don't miss using it in enterprise projects.
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#119Why did Google adopt the language for Android?
Re: If Java Is Dying, It Sure Looks Awfully Healthy
#120Earlier quoted context omitted.
> So, how again can something written in C perform faster than...something written in C? Easy. JVM has runtime information it can use that C compiler simply doesn't have. There are some synthetic benchmarks that show how "java is faster than C".
doesnt matter,the jvm takes a lot of resources which is problematic is some situations.raw speed is nothing without the memory footprint or AAA games would be written in java.they are not for a good reason:lack of direct memoy management.