News for hackers. Stuff that matters.
Re:The Simplicity of Single-File Golang Deployments by Asdrubalini on Wednesday March 22, 2023 @01:20PM (#35264197)
Rust's philosophy (unlike Python's, for example) consists in not including tons of stuff in the standard library, this way you can choose the best implementation for your specific use case from one of the many crates (which are super easy to install, by the way). There is no "always the best" implementation for a specific functionality, nor a legacy-but-still-officially-supported-in-std implementation that nobody uses anymore but still needs to be maintained with its own namespace.

I don't see this as negative or "reinventing the wheel". Reinventing the wheel would be writing your own implementation, which doesn't happen if you can choose from many high-quality crates.

Re:The Simplicity of Single-File Golang Deployments by abtinf on Wednesday March 22, 2023 @02:01PM (#35264796)
> legacy-but-still-officially-supported-in-std implementation

There is massive value in this.

Re:The Simplicity of Single-File Golang Deployments by Asdrubalini on Wednesday March 22, 2023 @04:50PM (#35266902)
Not officially supported doesn't mean not updated or not supported in general.
Re:The Simplicity of Single-File Golang Deployments by lenkite on Wednesday March 22, 2023 @03:11PM (#35265801)
"a legacy-but-still-officially-supported-in-std implementation that nobody uses anymore but still needs to be maintained with its own namespace."

The cardinality of the set of "nobody uses anymore" is usually in tens of millions.

Re:The Simplicity of Single-File Golang Deployments by Asdrubalini on Wednesday March 22, 2023 @04:51PM (#35266923)
If something is used by tens of millions, be sure that it will be updated even if legacy. Just not officially by the people who maintain the language.