3 ms·
"Why on Earth would you voluntarily code in a language where people can debate something as simple as which type to use for integers, unless you absolutely had
by kbart 11y ago
"Why on Earth would you voluntarily code in a language where people can debate something as simple as which type to use for integers, unless you absolutely had to?"
Because we have no alternatives so far. I do C programming for a living, but I'd be more than happy if there were some type and memory safe language I could use to program any tiny, obscure MCU, that could stay at least in the same order of magnitude of speed and let access hardware easily. Rust might be a step in a right direction, but it still has a looong way to go to become a viable alternative to C in embedded world. Of course, for a modern, high level development (web, mobile etc.), I see no reason to use C (maybe except for tiny libraries or co-routines where speed is critical). C is simply a tool -- it's neither good, nor bad -- and as every tool, it has it's use. You can easily break your fingers with a hammer, but that doesn't mean that it's a bad tool for driving nails in.
- oldmanjay 11y agoYou're aware that "we have no choice" does not answer a question about why you would do something voluntarily, right?
- kbart 11y agoI just confirm, that majority of C programmers nowadays do that because of "they absolutely had to".
- briansmith 11y agoWhat do you think Rust needs to do to become viable in the embedded world?
- kbart 11y agoEcosystem and community. Most of the time you can find what you need in C already written, in Rust it's do-it-yourself now.