3 ms·
Shortsighted discussion. C’s integers being wobbly-sized is the reason we have C compilers for pretty much every conceivable cpu architecture and we only have
by znpy 2y ago
Shortsighted discussion.
C’s integers being wobbly-sized is the reason we have C compilers for pretty much every conceivable cpu architecture and we only have rust/swift/other compilers for a handful of carefully picked architecture.
There are entire industries where C-as-a-protocol is fine enough (and actually appreciated, even though the author doesn't like it).
There are entire industries that do not use X86 or ARM, let alone RISC-V. There are many use-cases for MIPS, weird/other architectures (PowerPC, 8051, m68k-derivatives, pic-micro)... I had a relative that used to work on control software for space stuff, the CPUs used there are even older and definitely not x86/x86-64, arm or risc-v).
So yeah, complaining that the C language does not fit your own very specific use case is very shortsighted.
We should all remember that the world does not revolve around us and around our own use case.
- P_I_Staker 2y agoYeah, part of the problem is bias of computer scientists, which I've also seen on SV-centric communities like HN. A while back there was a complaint that CAN communication should be explained as it's "too obscure". So much obscure tech is talked about on this site without explanation. I think most of the developers on this site don't understand the wide world of embedded systems. C is a high-level language. It has a weird clunky elegance of it's own. Once you leave the world of servers and natively built apps on an OS, things get really complicated. Just go on Digikey, Mouser or whatever is big now and see how many processers are out there.