Hacker News Reader

Comment by anonova | Hacker News Reader

An officially supported Rust SDK should be a high priority, IMO. The de facto AWS library Rusoto (https://github.com/rusoto/rusoto) went into maintenance mode is in need of maintainers (https://github.com/rusoto/rusoto/issues/1651).

Microsoft has an Azure SDK under their organization (https://github.com/Azure/azure-sdk-for-rust), but oddly, it's marked as "unofficial". It looks like Google doesn't have one for GCP, but there is a community-built one: https://github.com/Byron/google-apis-rs

Given all these companies are part of the Rust Foundation (https://foundation.rust-lang.org/members/), maybe I just expect more.

View on HN

With all these big institutions around maybe some of them will get together and push for namespaces in crates.io?

It would be great if e.g. everything under "amazon/" could be trusted to be an official Amazon crate so you don't have to vet every dependency from every tutorial, and this seems like a common need for Amazon, Google and Microsoft.

See e.g. kibwen's comment at https://news.ycombinator.com/item?id=24445788 "The problem is that crates.io is a free, volunteer-run project with zero full-time employees who could be tasked with the drudgery of intervening in naming disputes or managing an identity layer. [...] Solve the funding issue first, and then you can start solving the rest."

I thought namespaces issue was solved in Java decades ago with domain names? Why invent anything?

The namespace issue was frequently brought up with the crates.io team on Discord, Github, and focus groups at various points over the life of the service. The takeaway is that the lack of namespaces isn't a funding issue, they did not, and still do not believe it is the right design. I personally don't think this is correct, and squatting is very prevalent right now. It's been a bit of a broken record at this point, but at the end of the day it's a volunteer run project and the volunteers that are willing to spend the time to maintain it don't want the feature. I think overall this is a pain point, but by no means a deal breaker.

I can confirm that I personally advocated for namespaces before Cargo existed. I failed to convince the decision makers.

Meanwhile, just a few days ago some of my project's crates were freshly squatted. Sigh.

Maybe someday they'll come around.

It looks like they have a job posting for this: https://www.amazon.jobs/en/jobs/1424393/software-development...

This is the big reason I still use Go for a few of my projects. I would prefer to use Rust but the lack or an SDK has me waiting.

Reply on news.ycombinator.com