Was Rust Worth It? (jsoverson.medium.com)

Article summary

The article's content is not available, but the discussion revolves around the design decisions of the Rust programming language, particularly regarding package management and naming. Commenters debate the pros and cons of Rust's approach, comparing it to other languages like Go and Java. The conversation touches on issues like namespace collisions, dependency management, and security. The discussion suggests that Rust's package manager, Cargo, has some drawbacks, such as a lack of namespacing and potential security risks.

Main themes

• package management
• namespace collisions
• dependency management
• security risks
• language design
• Rust vs other languages

What commenters say

• Rust's package manager, Cargo, lacks namespacing, leading to potential collisions and security issues.
• The use of URLs as package identifiers is seen as both a benefit and a drawback, with some arguing it allows for flexibility and others seeing it as a source of problems.
• Some commenters argue that Rust's approach to package management is flawed due to its lack of foresight regarding security concerns.
• Others see the current system as a necessary evil for gaining traction and allowing developers to fill gaps in the standard library.
• The comparison to other languages, such as Go and Java, highlights different approaches to package management and naming.
• There are differing opinions on whether the benefits of Rust's package management system outweigh its drawbacks.
• Some argue that the system's flexibility and ease of use are more important than potential security risks.
• Others believe that security concerns should take precedence and that the current system is inadequate.