4 ms·
The people making noise about unsafe C and then recreating Byzantine monsters are often the same camp; it's part of the normalized incentive to keep yourself em
by intelVISA 3y ago
The people making noise about unsafe C and then recreating Byzantine monsters are often the same camp; it's part of the normalized incentive to keep yourself employed by building Rube Goldberg machines for simple apparatus.
- Muromec 3y agoFor sure UBI will stop people from doing that if everyone id getting wort 300k of tax free credits so they can work on things that actually make the world better
- munk-a 3y agoIt feels unproductive to stage a discussion about anything around such unrealistic numbers. Very few people make 300k+, the average US salary is just under 60k.
- kkielhofner 3y agoI’ve experienced a strange phenomenon: The people who rant most (to zealot levels) about “unsafe C” are the most likely to write horribly insecure code in whatever their “safe” language of choice is. It reminds me of early aviation tech like computers, autopilot, fly-by-wire, etc. In many cases accident rates went up initially because pilots (very wrongly) assumed all of these magical newfangled technologies could just fix and handle everything. I’m not saying C isn’t fundamentally unsafe but your favorite memory safe language isn’t a cure-all and I can’t remotely understand how you could think it is.
- fn-mote 3y ago> The people who rant most (to zealot levels) about “unsafe C” are the most likely to write horribly insecure code in whatever their “safe” language of choice is. A longer story would be more convincing for those of us who have different experiences.
- intelVISA 3y agoWriting correct code is hard/tedious, as is writing C. You can extrapolate the rest.
- crest 3y agoIt's a lot easier to have no obvious flaws than obviously having no flaws. Complexity is one hell of a drug. sigh