4 ms·
That’s kind of like assuming AVR chips were only for hobbyists because you’re only familiar with the Arduino. And assuming that what hobbyists do has to be how
by bborud 3y ago
That’s kind of like assuming AVR chips were only for hobbyists because you’re only familiar with the Arduino. And assuming that what hobbyists do has to be how the embedded industry works.
I’m looking at this from the point of view of someone who runs a company that does about 2-3 custom MCU based design per year, and spends at least 30% of our software development effort on embedded. We don’t write firmware in C because it is fun, but because we don’t actually have any real choice.
But please, do tell me that I’m looking at this wrong when I say that I’d rather not write software that controls machines that can kill people in C.
- jmull 3y agoNo one is telling you what language to use for your purposes. Just trying to point out that not everyone has the same purposes, and therefore may correctly draw different conclusions.
- bborud 3y agoYou might want to figure out what actual challenges professional firmware developers face before you start assuming how they "correctly" draw conclusions.