Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
🤦 It's not necessarily about bugs in Rust-lang, though you can lookup CVEs if you want. The point is that ANY software, by default, will have bugs and exploits. Doesn't matter if it's Rust or C. You can exploit at the core, or at implementation. It's just matter of time and effort, as they say.
Just flat out saying Rust, or software written in Rust is be default is secure, is a fool's assertion. Sure it's LESS LIKELY to have a memory exploit, but that's where that assertion ends.
Who said that, Mr. Strawman?
It’s clearly better from both language feature and security standpoint and the community is behind it. What’s the problem?
did you mean to post a different link?