4 ms·

Sounds interesting. Could you explain how so?

simias 8y ago
Probably just a joke because of the tendency of Java applications (and other garbage collected languages to be honest) to consume an ungodly amount of RAM. Although these days I'd probably blame the web for that...
- Inityx 8y ago
  Not garbage collected languages per se; it's languages where data structures can't be value types[1], consequently consuming large amounts of extra memory because everything sits behind 2 or 3 or 5 layers of unnecessary 8-byte pointers. [1] https://en.wikipedia.org/wiki/Value_type_and_reference_type https://en.wikipedia.org/wiki/Value_type_and_reference_type
sdinsn 8y ago
He's just trying to bash Java. HN readers hate Java for some reason.
- kalleboo 8y ago
  Everyone I know in tech hates Java. They've all had to suffer through terrible poorly-performing Java desktop apps (or worse, applets) which has tainted the image of the language for a generation.
  - divan 8y ago
    Not supporting bashing language in this thread, but this was a reason I never wanted to develop in Java. This terrible desktop experience created a notable bias towards Java, and only later I learned that it's not that slow for networking services (but it was too late).
    - pjmlp 8y ago
      This terrible desktop experience was created by developers that didn't bother to learn Swing before they jumped into the keyboard. Writing everything on the main UI thread, not enabling system L&F, reading books like "Filthy Rich Clients", adopting third party Swing components with modern L&F....
    - sdinsn 8y ago
      I suggest you check out JavaFX. It is a mature, modern, flexible UI library that is now considered the standard. But of course, bad programmers make bad apps, no matter how good the ecosystem is.
  - sdinsn 8y ago
    I've found that terrible performing Java apps were created by terrible performing engineers. Java, from my experience, has always been quick and flexible.
- ADefenestrator 8y ago
  It's not 100% wrong. "Everything is an object" comes with some extra memory overhead, plus some GC accounting. Most garbage collectors need a decent amount of "slack" space to avoid OOM or long STW collections as well. So, I could see Java needing 1.5-4x the memory of C++ pretty easily anyways.

Probably just a joke because of the tendency of Java applications (and other garbage collected languages to be honest) to consume an ungodly amount of RAM. Although these days I'd probably blame the web for that...

Inityx 8y ago
Not garbage collected languages per se; it's languages where data structures can't be value types[1], consequently consuming large amounts of extra memory because everything sits behind 2 or 3 or 5 layers of unnecessary 8-byte pointers. [1] https://en.wikipedia.org/wiki/Value_type_and_reference_type https://en.wikipedia.org/wiki/Value_type_and_reference_type

sdinsn 8y ago

He's just trying to bash Java. HN readers hate Java for some reason.

kalleboo 8y ago
Everyone I know in tech hates Java. They've all had to suffer through terrible poorly-performing Java desktop apps (or worse, applets) which has tainted the image of the language for a generation.
- divan 8y ago
  Not supporting bashing language in this thread, but this was a reason I never wanted to develop in Java. This terrible desktop experience created a notable bias towards Java, and only later I learned that it's not that slow for networking services (but it was too late).
  - pjmlp 8y ago
    This terrible desktop experience was created by developers that didn't bother to learn Swing before they jumped into the keyboard. Writing everything on the main UI thread, not enabling system L&F, reading books like "Filthy Rich Clients", adopting third party Swing components with modern L&F....
  - sdinsn 8y ago
    I suggest you check out JavaFX. It is a mature, modern, flexible UI library that is now considered the standard. But of course, bad programmers make bad apps, no matter how good the ecosystem is.
- sdinsn 8y ago
  I've found that terrible performing Java apps were created by terrible performing engineers. Java, from my experience, has always been quick and flexible.
ADefenestrator 8y ago
It's not 100% wrong. "Everything is an object" comes with some extra memory overhead, plus some GC accounting. Most garbage collectors need a decent amount of "slack" space to avoid OOM or long STW collections as well. So, I could see Java needing 1.5-4x the memory of C++ pretty easily anyways.