News for hackers. Stuff that matters.

A comment on The benefits and costs of writing a POSIX kernel in a high-level language. Parent comment

Re:The benefits and costs of writing a POSIX kernel in a hig... by nickpsecurity on Monday October 08, 2018 @10:46PM (#18172964)
"So saying "just don't use GC" as a answer to improving throughput shows ignorance."

It could also mean they use Rust, memory pools, some kind of checker that catches those errors, or separation logic. Probably that order due to popularity.

As a counterpoint to "don't use GC," there's also low-latency or real-time implementations of RC/GC to consider as well. A lot of developers using RC/GC languages don't know they exist. Maybe we need a killer app that uses it to spread awareness far and wide. More open implementations of the concept, too.

[ Parent | on HN ]
Re:The benefits and costs of writing a POSIX kernel in a hig... by yoklov on Monday October 08, 2018 @11:48PM (#18173185)
> there's also low-latency or real-time implementations of RC/GC to consider as well

These exist but tend to have poor throughput, frequently set a maximum amount of memory you're allowed to use, and typically don't perform well when compared to commonly used garbage collectors.

[ Parent | on HN ]