It’s a shame that the ergonomic problems of Java-the-language obscure the really impressive technical achievements of the JVM.
-
-
Replying to @pcwalton
And this is why Kotlin and Scala (which I think had an influence on Rust) exist. But I think that introducing such a bloated thing like the GC wasn’t that good (except in Async programming) But honestly, it was revolutionary, but still inefficient in sync programming.
3 replies 0 retweets 5 likes -
Replying to @botros__fadi @pcwalton
ARC is eager and GC is lazy. This confers a ton of advantages for advanced generational/copying collectors like the JVM's: - Different allocation strategies for short vs long-lived objects - Better data locality - Better throughput because of the above and avoiding ARC busywork
1 reply 0 retweets 6 likes -
Replying to @bascule @botros__fadi
Note that barriers, needed for generational GC, make tracing GC “eager” as well. And advanced reference counting schemes like RC-Immix typically do some form of deferred reference counting, which is “lazy”.
1 reply 0 retweets 5 likes
You’re touching on what David Bacon describes in “A Unified Theory of Garbage Collection”: https://courses.cs.washington.edu/courses/cse590p/05au/p50-bacon.pdf …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.