← Back to context

Comment by SamInTheShell

18 hours ago

I don't think you understand the threading concurrency topic. Also memory safety is so far off base here, where's that coming from? Java does some stuff okay, but do you really want to defend the horrid JVM problems? Also why can't I have my memory back when it's not in use in tightly packed systems?

It's not great for everything and neither is Go. You can find a bit more context on that in some of the other threads.

9 comments

SamInTheShell

Reply
gf000  11 hours ago

> defend the horrid JVM problems

Such as? It's one of the most widely used platform for backend services, basically almost all top 500 company has some business critical infrastructure running Java. It surely can't have "too horrid" problems..

  • SamInTheShell  3 hours ago

    I gave an example. Go allocate 8 gigs. Then get it garbage collected. Why is JVM still allocating 8 gigs?

    • za3faran  2 hours ago

      We have Java services running on 512MB k8s nodes.

      Furthermore, collection time (for moving collectors) is a function of the liveset, not the # of dead objects.

  • jeremyjh  9 hours ago

    The JVM is awesome. The only problem with Java is all of the Java code that has ever been written.

Ygg2  11 hours ago

> Also memory safety is so far off base here, where's that coming from?

It's coming from Go. In presence of data races on interfaces, slices or maps your memory might get corrupted.

> Also why can't I have my memory back when it's not in use in tightly packed systems?

You can. You have to either set your GC to be more aggressive or you need to utilize value types more.

  • SamInTheShell  3 hours ago

    The memory safety thing is just a moot out of scope contract. It seems moot to me every time someone shows up trying to push memory safety everywhere, that's a language to developer contract issue, not a functionality issue. When the contract of the language is such as that of Go vs Rust, the two languages are just offering different contracts. Rust just promises to hold your hand more than Go does.

    Regarding the JVM and GC. Good luck with that? Every Java application I've seen in the wild when I supported JVM seemed to never release any ram it allocated. Ever. If it used 1G and even after free, the JVM decided that was going to be used again and wouldn't release it.

    It would be hard to sell me on wanting to use Java again (people can pay me enough to do it, but I hate it). Which kinda sucks since Apache Foundation has a ton of really cool projects using it. Kotlin maybe, but I have no real use cases where it would be better than anything else I know right now.