2 ms·
I'm not a "security expert", but it seems to be problem #1 with your approach is that C just totally dominates the mindshare in the embedded space, and until yo
by jerf 17y ago
I'm not a "security expert", but it seems to be problem #1 with your approach is that C just totally dominates the mindshare in the embedded space, and until you solve that problem and its underlying causes, you have lost before you start. The average developer simply doesn't think security is a problem unless you exploit it right in front of them, a goodly number of those people will still deny it's a problem, and a good fraction of those who do agree it's a problem will declare that only C has the performance they need, with no interest in either a debate about the matter or the presentation of a language just as performant as C but also more secure.
Personally, I value security, and I think the evidence at this point is that you have to be a freaking genius to almost correctly code C programs and that's just not scalable, and thus the first thing I'd do is cross C off my list and just live with the results... but then, I'm not an embedded programmer, either. It was time for C to be taken out back and shot in 1980, before the world was networked together, but here it still is, providing us exploits by the cartload. Hooray.
("What should have replaced it, then?" Pick your choice of safe C dialect, which is a productive Google term. I don't deny C's performance or nature as "portable assembler", what I deny is that either of those two things necessarily requires security vulnerabilities to come in by said cartload.)
- stcredzero 17y agoI'm not a "security expert", but it seems to be problem #1 with your approach is that C just totally dominates the mindshare in the embedded space, and until you solve that problem and its underlying causes, you have lost before you start. "My approach" is not to do all embedded development in Smalltalk. I'm only applying facts from the language I know the best (not only as a user but from an implementation standpoint) to discuss what must be possible.
- jerf 17y agoI was taking your larger first sentence. You don't even necessarily have to freak out an embedded programmer to get closer to secure, there are a variety of "safe" C dialects. (I don't know enough about them to even begin to judge them, but I don't deny that it ought to be possible.) But I do think once you shook The Establishment free of C that they would not necessarily move to C+-; there would be a window to wedge some other things in there.