AWS' Sponsorship of the Rust Project
aws.amazon.com
aws.amazon.com
Source: https://aws.amazon.com/blogs/opensource/aws-promotional-cred...
> ps – AWS credits are available for other open source projects!
it sounds like it
"We’re thrilled that AWS, which the Rust project has used for years, is helping to sponsor Rust’s infrastructure. This sponsorship enables Rust to sustainably host infrastructure on AWS to ship compiler artifacts, provide crates.io crate downloads, and house automation required to glue all our processes together. These services span a myriad of AWS offerings from CloudFront to EC2 to S3. Diversifying the sponsorship of the Rust project is also critical to its long-term success, and we’re excited that AWS is directly aiding this goal." https://aws.amazon.com/blogs/opensource/aws-promotional-cred...
* https://internals.rust-lang.org/t/which-ci-platform-should-r...
* https://internals.rust-lang.org/t/update-on-the-ci-investiga...
PS. The comment on the reddit thread is from one of the co-authors of the blog announcing the sponsorship.
The rust devs recompile a huge chunk of the entire rust ecosystem to make sure new compiler versions don't break things.
I can't imagine something like this being even close to feasible in the C++ ecosystem; there is too little standardization of build tooling, too much brittle/broken code.
Still it's not cheap and Amazon is paying, bless their hearts and excess compute capacity when it's not Christmas.
That being said, there is nothing preventing something similar with C++.
In fact, that's pretty much what Linux distributions and BSDs do when upgrading the compiler, see for example https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240629
I think Rust will see huge growth from best of breed WebAssembly tools to the really small/fast libraries available. I'm not that deep, but it's been an interesting learning curve. Hoping to find a couple things to actually work on in terms of projects this coming year with it.
Edit: I am curious if we'll see some Docker tooling move towards Rust, most of that is currently Go, though some of the wasm stuff might be a better direction vs. containers.
https://mobile.twitter.com/solomonstre/status/11110049132223...
I can’t imagine why...
How do you know what's interesting to me?
And I didn't downvote you - I can't possibly have done, can I, because you can't downvote a reply to your own comment on Hacker News.
I'd say it's rude in general to tell someone they won't find something interesting, and especially so when it's done as a way of disowning your own preference not to talk about it.
For example, when people ask what I do, I could say I work at an ISP, or that I'm a systems engineer (my title), or that I'm a system administrator (some of what I do), or that I'm a software developer (the rest of what I do), or any number of other things. Depending on how interested in it I think they will be, or how interested in explaining it I am, I might respond that it's likely not that interesting.
If the person asking actually wants to pursue it further, the polite thing to do would be to say "oh, I find it interesting, if you're willing to talk about it". If they responded "How do you know what's interesting to me?" I would take that as somewhat aggressive, and definitely wouldn't be interested in explaining further, depending on how I perceived their disposition.
Perhaps it's a cultural miscommunication.
If they get aggressive and you then decide that you don't want to explain, that's fine. But that's not what happened here.
Eh, I don't think you can say that definitively. I took it as WaxProlix not wanting to/being unwilling to talk about it because it's boring, and as they found it boring, they thought other people would likely (the word they used, which I think people are ignoring) find it boring as well.
They apologized to the person they said it to, and it all seems settled from my perspective.
Amazon rarely likes to talk about how things are built at the nuts and bolts level.
[1] https://www.amazon.jobs/en-gb/search?base_query=ruby+on+Rail...
Ruby is a frequent scripting language at Amazon. JRuby on Rails is (or was) a solid way to get a nice web app running for internal use without interfacing with Spring. The AWS SDK is pretty great for internal tools that need to interact with S3.
It honestly isn't super interesting, but it's a well-supported platform internally.
Python gets some dislike, and there are a few significant projects trying to get off it. As a blanket statement I don't think dynamic languages work well at a company like Google.
Looks like AWS is echoing that sentiment:
Performance. Rust is blazingly fast and memory-efficient: with no runtime or garbage collector, it can power performance-critical servicesRuby even excluded from GSoC while python isn't.
it is all about tooling and dev support. ruby wasn't landed properly