For Better Computing, Liberate CPUs from Garbage Collection

Re:For Better Computing, Liberate CPUs from Garbage Collection by simiones on Thursday May 09, 2019 @08:08AM (#19867453)

The nicest point about GC is that, for the vast majority of data, you no longer need to have a concept of ownership at all.

Ownership is not a fundamental architectural property - it is "only" a powerful technique for tracking data with a specific lifetime (of course, even in GC languages you still need proper ownership semantics for some pieces of data).

[ Parent | on HN ]

Re:For Better Computing, Liberate CPUs from Garbage Collection by blub on Thursday May 09, 2019 @09:19AM (#19867984)

Ownership itself might not be, but lifetimes are and the two concepts are tightly related.

That's why Java and C# both had to introduce a way of (semi-)automatically closing resources, waiting for the GC was a catastrophe.

[ Parent | on HN ]

Re:For Better Computing, Liberate CPUs from Garbage Collection by pjmlp on Friday May 10, 2019 @07:41AM (#19876837)

Common Lisp, CLU, Mesa/Cedar, Modula-3 and many other system languages with GC always supported those kind of mechanisms.

Java and C# did nothing new there, only catching up with was already the state of the art before they were born.

[ Parent | on HN ]

Re:For Better Computing, Liberate CPUs from Garbage Collection by maxxxxx on Thursday May 09, 2019 @10:24AM (#19868540)

That’s what I find ironic about C#. In some ways I worry more about and do more manual memory management than I did in C++.

[ Parent | on HN ]