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 stcredzero 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.
"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.