zlacker

[return to "Rust in the NetBSD Kernel, and other odd decisions"]
1. akagus+bQ[view] [source] 2026-02-03 10:46:39
>>jaypat+(OP)
We need memory safety but Rust is not the answer.

It has no formal spec, changes too fast, depends on third party libraries that change faster than I can breath, and is controlled by a foundation that is controlled by big tech corps.

What could go wrong?

◧◩
2. pjmlp+z21[view] [source] 2026-02-03 12:16:57
>>akagus+bQ
It has a partial spec.

https://ferrous-systems.com/blog/ferrocene-25-11-0/

Lets not forget not having a formal spec apparently wasn't an issue for C, which only got standardized in 1989, and even K&R C only specified a subset of its behaviours, which is a reason why there is so much UB, and implementation specific behaviours with YOLO C, as the Fil-C author likes to call it.

[go to top]