Re:Overestimation of microplastics potentially caused by sci...
by refulgentis on Sunday March 29, 2026 @11:56AM
(#47564263)
That's the analogy working as intended: the answer to "why do programmers still write memory-unsafe code" is the same shape as "why do microplastics researchers still wear gloves." The real answer is boring and full of tradeoffs. The HN thread version skips to indignation: "they never thought of contamination so ipso facto all the research is suspect"
(to go a bit further, in case it's confusing: both you and I agree on "why do people opt-in to memunsafe code in 2026? There’s no reason to" - yet, we also understand why Linux/Android/Windows/macOS/ffmpeg/ls aren't 100% $INSERT_MEM_SAFE_LANGUAGE yet, and in fact, most new written for them is memunsafe)
Re:Overestimation of microplastics potentially caused by sci...
by peyton on Sunday March 29, 2026 @03:12PM
(#47566195)
You’re ignoring the article to grind your axe.
Re:Overestimation of microplastics potentially caused by sci...
by refulgentis on Sunday March 29, 2026 @06:18PM
(#47567993)
What do you mean? (Genuinely seems you replied to wrong comment to me. What axe? What’s in the article that’s been ignored?)
Re:Overestimation of microplastics potentially caused by sci...
by nineteen999 on Monday March 30, 2026 @10:44AM
(#47575023)
They may have meant .exe
I used to be a code monkey, I wrote systems software at megacorps, and still can't understand why so many programmers irresponsibly write memory unsafe code given it has a global impact.
So Poe's law applies here.