Conversation

My strong feeling is that the "memory safe systems programming language that's easier to use than Rust" that everyone wants is going to have to have something that looks a lot like a garbage collector. There's a lot of room to design a fast GC for "systems-like" patterns.

369

Replying to

You cannot have a safe language without ownership and lifetimes and also without a GC. Ownership and lifetimes are essential complexity in safe languages. But I doubt a fast GC optimized for systems like patterns will be useful in practice

Replying to

and

Java is heavily used without any GC in secure element environments. Developers need to use object pools to reuse objects since they can't be released. There are many other examples of safe languages without either of those things. You can also simply only provide value types.

5:25 AM · Jul 28, 2022Twitter Web App

Replying to

and

Java Card 3.0 introduced GC support but that's barely used by anyone. Java Card 2.x didn't have GC and the vast majority of secure elements including SIM cards, NFC and others (NXP, etc. SEs used in many products) lack it. Other examples like it but probably not as broadly used.

Replying to

and

I am sorry but your statement is wrong. JCSystem.requestObjectDeletion() exists since JavaCard 2.2 which is year 2002. It doesn't have automatic GC but on request.

Show replies