Our great sponsors
-
containers-roadmap
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Energy-Languages
The complete set of tools for energy consumption analysis of programming languages, using Computer Language Benchmark Game
> What kind of plans for support of Rust's evolving async ecosystem?
We were hoping async-function-in-trait would land before GA, however, we have a plan to add support in a backwards compatible way when it's released.
> Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps?
Our roadmap has unfortunately been in a state of disrepair for some time. We're hoping to get it cleaned up and accurate post GA.
> Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically AWS SDKs have been inconsistent on. Just a request not really a question :-)
There are lots of examples here [1], some simple, some quite complex. If there's something you have in mind, please file an issue! Having great examples is one of our priorities.
[1]: https://github.com/awslabs/aws-sdk-rust/tree/main/examples
Thanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
I've been testing this for a while!
One thing I sorely missed was workers for consuming SQS messages. Ended up having an intern adapt a worker for the old community AWS SDK (rusoto) into this: https://github.com/Landeed/sqs_worker
Trawling through the wayback machine, I did find that the older pages link to https://github.com/greensoftwarelab/Energy-Languages, which does seem to provide the contents of the specific programs used and the benchmarking software. Excellent.
Related posts
- Joke of the day (science paper about language efficiency), their C++ examples are an absolute nightmare
- Terraform vs. AWS CloudFormation
- Building an Amazon Location Service Resources with AWS CDK and AWS CloudFormation
- Scaphandre: Bring back energy consumption to your metrics
- C Is the Greenest Programming Language