4 ms·

I don't think that's the root problem. I think C programmers don't believe C is a problem. New software is started every day on C. There's no excuse for that a

I don't think that's the root problem. I think C programmers don't believe C is a problem. New software is started every day on C. There's no excuse for that and no financial incentive to do it. If the engineers actually admitted that C is not a safe languages for shipping software, then we could at the very least freeze the existing code and write everything _new_ in a same language. But we don't. Engineers still go starting brand new greenfield projects in C which is just insane.

optymizer 2y ago
Just because you don't understand it, doesn't mean it's insane. It just means that your view of the world is different from others.
rfoo 2y ago
> then we could at the very least freeze the existing code and write everything _new_ in a same language Sure, if you are willing to help, here's my wishlist: - I wish we can freeze libssh and write everything new in Rust. - I wish we can freeze CPython and write everything new in Rust. - ... Can you do it for free? At work I'm busy maintaining old projects in C++ and writing new ones in Rust. Since I'm not getting paid to rewrite or maintain our dependencies full-time I can't do above. Oh, I'm not paid to initiate an effort to freeze our old projects either. If this sounds too harsh: - I wish we can freeze ZMK [1] and write everything new in Rust (or Zig, though it's not memory safe, whatever). That's about one of my hobbies and I always wanted to do it. [1] https://github.com/zmkfirmware/zmk https://github.com/zmkfirmware/zmk