Post AaodLRwFso0L2KpNzs by AlgoCompSynth@ravenation.club
(DIR) More posts by AlgoCompSynth@ravenation.club
(DIR) Post #AaoZRRyyEX3v5qhh9U by inthehands@hachyderm.io
2023-10-16T02:33:17Z
0 likes, 0 repeats
This bang-on post from @airspeedswift is not getting the attention it deserves:https://mastodon.social/@airspeedswift/111234020859557888
(DIR) Post #AaoZRZlnHPH9FIbHiy by chrisamaphone@hci.social
2023-10-16T02:54:37Z
0 likes, 0 repeats
@inthehands @airspeedswift … i feel like i’m missing some context. memory safety is generally taken as a given in most contexts, except where fine grained control is considered necessary, so where are folks arguing about this? rust vs c or something?
(DIR) Post #AaoZRfgLIaTpa8613o by inthehands@hachyderm.io
2023-10-16T03:09:16Z
0 likes, 0 repeats
@chrisamaphone @airspeedswift Yes, in C/C++, which still accounts for a •substantial• portion of new code written, and of code in production, and of critical vulnerabilities.The C++ world in particular has been in turmoil in recent years over the battle between “just don’t write bugs” vs “mitigate with better tooling” vs “C/C++ are the cigarettes of p-langs.” This in particularly set the cat amongst the pigeons:https://media.defense.gov/2022/Nov/10/2003112742/-1/-1/0/CSI_SOFTWARE_MEMORY_SAFETY.PDF
(DIR) Post #AaoZRjyZKlR6toed1c by jeff@misinformation.wikileaks2.org
2023-10-16T03:10:52.889677Z
0 likes, 0 repeats
@inthehands @chrisamaphone @airspeedswift you have the same problems in "safe" languages like rust, they just lie about it.
(DIR) Post #AaoZeLDogEgntGnKim by inthehands@hachyderm.io
2023-10-16T03:12:22Z
0 likes, 0 repeats
@jeffYeah, no, sorry. This is wildly, fantastically, pants-on-head incorrect. You have a whole new set of very •different• problems.
(DIR) Post #AaoZeM01mzFoInLprs by jeff@misinformation.wikileaks2.org
2023-10-16T03:13:18.194590Z
0 likes, 0 repeats
@inthehands go look at the CVEs for the rust stdlib in the last 2 years and tell me i'm wrong.
(DIR) Post #AaoaLFXHhEmshwMRMm by inthehands@hachyderm.io
2023-10-16T03:14:30Z
1 likes, 0 repeats
@jeff You’re wrong. There’s even a study.https://dl.acm.org/doi/10.1145/3466642
(DIR) Post #AaoaLJj878dhhpvxNw by jeff@misinformation.wikileaks2.org
2023-10-16T03:21:02.845693Z
0 likes, 0 repeats
@inthehands alright fair. i still deeply despise the religious fervor from the rust people over not using their half baked nih solutions to mostly solved problems.
(DIR) Post #AaodLPzj6vap0WR888 by inthehands@hachyderm.io
2023-10-16T03:11:19Z
0 likes, 0 repeats
@chrisamaphone @airspeedswiftI think it’s hard for those of us who haven’t done serious work in C or C++ for ages (~25 years in my case), or who never have at all, to appreciate just what a large portion of the greater software development world those few remaining memory-unsafe languages still occupy.
(DIR) Post #AaodLQv9fPWvsdIzdw by AlgoCompSynth@ravenation.club
2023-10-16T03:36:23Z
0 likes, 0 repeats
@inthehands Oh, we appreciate it, but it falls into the class of accepting the things we cannot change.I've never had to learn C or C++ and now I have no desire to either. And I am coming to the conclusion that a project whose only documentation is C source code is a waste of my time.
(DIR) Post #AaodLRwFso0L2KpNzs by AlgoCompSynth@ravenation.club
2023-10-16T03:40:29Z
0 likes, 0 repeats
@inthehands Case in point for the latter - the Raspberry Pi Pico examples for generating audio via PWM or an I2S DAC.
(DIR) Post #AaodLSjsuHhfWG31M0 by inthehands@hachyderm.io
2023-10-16T03:44:23Z
1 likes, 0 repeats
@AlgoCompSynth The irony is something like generating audio on a Pi is totally something a memory-safe lang could do. Opening the door to memory errors for no reason!