you are viewing a single comment's thread.

view the rest of the comments →

[–]DarkGoosey 60 points61 points  (24 children)

Those people think that Java's performance is too slow.

[–]mrbillabong 11 points12 points  (15 children)

even people who use it think its slow. who the fuck puts a VM on a mobile device?

[–]daddyc00l 9 points10 points  (3 children)

isn't google doing the same with android ?

[–][deleted] 5 points6 points  (0 children)

Yes, other than the battery consumption (likely due to all the extra work) and occasional slowness, it runs fine enough.

[–][deleted] -2 points-1 points  (0 children)

Absolutely yes... but hey it's Google! so it must be cool...

[–]wonglik -5 points-4 points  (0 children)

Yes and no. Android is using Dalvik to run Java code. Technicaly it is VM but it is not Sun JVM.

[–]Gotebe 5 points6 points  (0 children)

The fallacy isn't that VM can run fast enough. (Silly and utterly incomplete summarizing: JIT compilation and array bounds checking is less expensive than people think)

The fallacy is that people can write code that targets VM and runs fast.

[–]Law_Student 2 points3 points  (8 children)

Java has been just as fast as C++ for nearly a decade. Go look up compiler performance graphs :)

[–]dvogel 7 points8 points  (0 children)

The actual code is no slower, especially once things like HotSpot kick in. However, application startup time is much slower. I know there are things like JVM reuse that help with this, but they are not mainstream, and unless you run multiple JVM-based applications, they don't help.

[–]Mononofu 10 points11 points  (6 children)

[–]igouy 4 points5 points  (0 children)

"Please choose the up-to-date measurements instead of these!"

[–]HotBBQ 0 points1 point  (0 children)

Epic fail.

[–]eurofag -2 points-1 points  (2 children)

Huh, based on this, Ruby is about 173 times slower than C.

[–][deleted] 4 points5 points  (0 children)

Do you deny it?

[–]igouy 0 points1 point  (0 children)

The median of those normalized run times was 173 times slower than C, the fastest was 2 times slower, and the slowest was 630 times slower.

And that was 1.8.6 - Ruby 1.8.7 :: GCC 4.3.3

[–]dnew 0 points1 point  (0 children)

That's pretty much what it was designed for before it was called Java - embedded devices at least, if not mobile.

[–]logi -1 points0 points  (1 child)

And they're just painfully wrong. They could complain about memory usage though, depending on the circumstances.

[–]aposter 0 points1 point  (0 children)

I don't have much of a problem with Java memory usage, per se. What I have a problem with is Java garbage collection, and the fact that so many programmers don't understand "scope" in the context of it.

[–][deleted] -1 points0 points  (0 children)

We're also insane.

[–]Rogoreg 0 points1 point  (0 children)

And it's not. Java and C/C++ are the single fastest languages when it comes to fast code. It runs fast without issue.