4 ms·
Fil-C[0] can compile GNU coreutils, it has stronger* memory safety guarantees than rust, none of the compatibility issues that a wholesale rewrite has, and perf
by WatchDog 19d ago
Fil-C[0] can compile GNU coreutils, it has stronger* memory safety guarantees than rust, none of the compatibility issues that a wholesale rewrite has, and performance that seems to be within about a factor of two[1] compared to the normally compiled code..
[0]: https://fil-c.org/ https://fil-c.org/.
[1]: https://bannalia.blogspot.com/2025/11/comparing-run-time-performance-of-fil-c.html https://bannalia.blogspot.com/2025/11/comparing-run-time-per...
* Guaranteed to crash rather than potentially grant arbitrary code execution.
- quotemstr 19d ago"Stronger" is absolute bullshit. No data race prevention. No intra-object protection. Mandatory GC, and 5x the compute cost. Nothing like a statically safe language.
- logicchains 19d agoIt's coreutils, there shouldn't be any threads to be data racing.
- tcfhgj 19d agoHaven't threads been one of the reason some core util got faster?
- collinfunk 19d agoOnly GNU sort uses threads. There is still some room for improvement there, if anyone wants to take a shot at it. :)
- zamadatix 18d agoI think I saw the Rust based implementations sometimes used a separate thread for background tasks like statistics reporting. Not much additional in the way of "directly" using threads, but I wonder how many could actually be any faster with direct threading.