I agree the claim of "memory safe" is not "strong" in the sense of formal verification.
But the goal was to bring verification techniques (type systems, ownership and lifetime tracking, etc) to a practical language that also supported efficient interop with existing C libraries and APIs. Hence the 'unsafe' keyword. At this, Rust has succeeded wildly.
I've been writing Rust for years and almost never need to use 'unsafe'.
They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure.
I know this sounds harsh but it really would be better for the world if these "processing complex untrusted data structures in C" enthusiasts found another hobby.
> They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure
Typically it's presented as-is and without any form of warranty, but in the hope it will be useful - not "suitable for critical infrastructure".
Perhaps those using it for "critical infrastructure" can write their own utilities, or chip in to support the developer whose hard work they apparently rely so heavily on, so bug fixes aren't done merely in the dev's unpaid time-off?
"Critical infrastructure" wasn't my phrase and I agree that the corporations who are using open source have a moral and pragmatic obligation to fund its maintenance.
But what does a developer (open source or not) who releases a container format parser and codec collection upon the world expect people to do with it if not run it on malicious data on personal devices?
> But what does a developer who releases [...] upon the world expect people to do with it
Sometimes you build things to explore how they work, or to test your assumptions about how something would work. To build your own knowledge about a format, language, or system. Hell, sometimes it's just the middle of a venn diagram between fun and practice.
And, because it's easy to throw something up on GitHub, you can say "Look at this cool thing I made", "Look, I actually can do what I claim on my resume", or "Anyone struggling in the same place as me can use this as an example workaround, or inspiration for a solution"
Nobody has to, or is even necessarily expected, to use it. Sometimes it's just the author sharing this cool thing they made.
This is normal and expected activity. We encouraged our users to write canonical answers, that could be run as community wikis (not everything got converted to a wiki, but many things did). One of the reasons was to take a spot in the top 3 on a search engine, in an attempt to displace some horrendous / ad riddled website that at best a bad user experience, and frequently was subtly wrong or incomplete.
Some examples: we settled on a canonical answer for “how to install packages in Ubuntu”, or when there was a particularly interesting question that was discussed in the chat rooms, someone might volunteer to consolidate that information and publish the Q&A as a wiki.
It’s just internet points. They’re not worth much.
Activity simulators, they're called. A good way to make a web site feel alive even with no or few human visitors. 4chan does this. Reddit. X/Twitter. And others...
reply