11–19 of 19 posts
[1]: https://github.com/rust-stdx/stdx/commit/550c11b75804392e366...
...but why? Seriously, this needs some more justification: > Only big and well-funded organization are able to build the internal tooling and libraries requireed to securely ship large Rust projects. Leaving aside the (real!) problems other commenters have highlighted, before even getting to those issues I have a small foundational question: Is this actually a real problem?
The author is an individual claiming the ability to author and maintain a standard library
… to be used by small orgs who do not have the resources to author and maintain a standard library.
This is a collection of forked open source crates bundled together with open model vibe coding? > the code written by AI is more robust than by humans because more edge cases are tested. This is at least a mildly concerning take to see in a blog post announcing a solution to supply chain security. It seems like this boils down to: don’t trust the original authors to maintain the packages they wrote, trust me and my L…
- No mention of what specifically it does
- No mention of the advantages and stated reasons for having small std and core libs
- Libs mentioned as being "shipped" by the author have no commits by him or her.
- No comparison in the specifics to how it's handling
- Uses phrasing which might (IMO deliberately) confuse people into thinking this is official....but why? Seriously, this needs some more justification: > Only big and well-funded organization are able to build the internal tooling and libraries requireed to securely ship large Rust projects. Leaving aside the (real!) problems other commenters have highlighted, before even getting to those issues I have a small foundational question: Is this actually a real problem?
> Cryptographic code is famously hard, with many, many footguns haunting unsuspecting developers (and even experts!). > But, cryptography also has something that you likely won't find in any other domain: an extensive public collection of test vectors, particularly for edge cases. Every algorithm specification come with a basic suite of test vectors, but there are also community-built wonders such as Wycheproof. > Th…
> Cryptographic code is famously hard, with many, many footguns haunting unsuspecting developers (and even experts!). > But, cryptography also has something that you likely won't find in any other domain: an extensive public collection of test vectors, particularly for edge cases. Every algorithm specification come with a basic suite of test vectors, but there are also community-built wonders such as Wycheproof. > Th…
If you're building a dashboard for visualizing something fun (hot dog sales in sport games) then the corner case error has low cost. I'm happy having this vibe coded dashboard that works 99/100 and my world is better with it existing.
Crypto is on the opposite scale (and I'm surprised this blog doesn't realize it): 9999/10000 isn't good enough because the corner cases have dire consequences. So, yeah, bad example for vibe coding
...but why? Seriously, this needs some more justification: > Only big and well-funded organization are able to build the internal tooling and libraries requireed to securely ship large Rust projects. Leaving aside the (real!) problems other commenters have highlighted, before even getting to those issues I have a small foundational question: Is this actually a real problem?
The proposed solution conflicts with the supposed problem. The author is an individual claiming the ability to author and maintain a standard library … to be used by small orgs who do not have the resources to author and maintain a standard library.