When you’re working at a real systems level c is so much easier to get up and running with. These are hard problems and getting something just to a working stage can be a real challenge. C is also really simple in comparison to those mentioned, and there are a lot of people that enjoy working with c/asm.
Zig is not stable and will not be for sometime. It has a few quirks that bother me, but I look forward to using it more seriously once they release 1.0.
Rust is a different style of programming, that’s not a bad thing, but you can’t fault someone for not liking it. I think it’s great that a lot of people really like rust, that’s awesome, but it’s not perfect. It doesn’t help that there’s a lot of condescension towards other languages coming from rust zealots.
Go’s GC makes it a non starter in certain domains.
C ‘package management’ isn’t that difficult once you understand the tooling, and there’s a lot of freedom that you come to appreciate when you’re writing a driver, bootloader, porting to a custom/exotic os, etc. clangd works fantastically so it’s not lacking lsp goodies.
Real systems programming is a much smaller field than other disciplines so it does not surprise me that programmers as a whole don’t understand what makes c great.
At the kernel level you’re not going to be using package managers, or anything with a GC (rip D)
I don’t think C is particularly good, but it’s “good enough”, and nothing obviously better at these use cases has come along to displace it. It’s been around long enough that it “just is” the tool of choice for stuff for people.
Which of course leads to things like the Linux situation where it’s big enough that nobody actually understands how it all works or fits together.
Sounds more like Linus is keeping up face after the rust debacle.
Honestly who the hell would want to code in C? when you have better languages like zig,rust,go with actual package management, linters
Go is not something you can use for systems programming.
When you’re working at a real systems level c is so much easier to get up and running with. These are hard problems and getting something just to a working stage can be a real challenge. C is also really simple in comparison to those mentioned, and there are a lot of people that enjoy working with c/asm.
Zig is not stable and will not be for sometime. It has a few quirks that bother me, but I look forward to using it more seriously once they release 1.0.
Rust is a different style of programming, that’s not a bad thing, but you can’t fault someone for not liking it. I think it’s great that a lot of people really like rust, that’s awesome, but it’s not perfect. It doesn’t help that there’s a lot of condescension towards other languages coming from rust zealots.
Go’s GC makes it a non starter in certain domains.
C ‘package management’ isn’t that difficult once you understand the tooling, and there’s a lot of freedom that you come to appreciate when you’re writing a driver, bootloader, porting to a custom/exotic os, etc.
clangdworks fantastically so it’s not lacking lsp goodies.Real systems programming is a much smaller field than other disciplines so it does not surprise me that programmers as a whole don’t understand what makes c great.
I’ve yet to see any actual condescension from Rust developers, just a whole lot of people complaining about Rust.
At the kernel level you’re not going to be using package managers, or anything with a GC (rip D)
I don’t think C is particularly good, but it’s “good enough”, and nothing obviously better at these use cases has come along to displace it. It’s been around long enough that it “just is” the tool of choice for stuff for people.
Which of course leads to things like the Linux situation where it’s big enough that nobody actually understands how it all works or fits together.