can't believe it's 2025 and people are programming in memory unsafe languages like Rust and Go when Fil-C exists
Thread
Login to reply
Replies ()
@npub15rp4...wudh huh fascinating.
> All memory safety errors are caught as Fil-C panics.
So… sorta segfaults? You still have the problem of writing unergonomic C/C++, but at least it won’t be a security issue 😂
> Fil-C achieves this using a combination of concurrent garbage collection and invisible capabilities (InvisiCaps).
Huh… I wonder what the perf hit / jitter are like. That’s the reason many of us abandoned GC.
@npub15rp4...wudh this is amazing