News for hackers. Stuff that matters.

rusbus

Re:Principles for Fast Tokio Applications on Monday September 14, 2026 @06:20PM (#49705003)
(I am OP) Both good call outs. Will update the article to include them
Re:Principles for Fast Tokio Applications on Monday September 14, 2026 @04:30PM (#49703483)
Was this in a specific application? I wouldn't necessarily expect that histogram to be particularly bad for most applications.
Re:Principles for Fast Tokio Applications on Monday September 14, 2026 @04:28PM (#49703451)
Do you have any resources worth referencing on this? I assume this isn't something that works with tokio more of a replace tokio?
Re:Principles for Fast Tokio Applications on Monday September 14, 2026 @01:59PM (#49701125)
Note that most of those end up getting inlined in practice
This is exciting because the effect size is so large. But as the author's acknowledged, selection bias is nearly impossible to control for in this non-randomized study:

> and lacks randomized controls. Self-selection is the central threat: students who complete more quizzes may be more motivated or higher-performing generally

But this is still a strong result. I'm excited to see more in this space.

Two years ago someone told me "I wish I could understand what Tokio is actually doing."

This really stuck with me and earlier this year I had both an idea and the time to try to make it happen. I think with dial9 that is finally possible. dial9 is a system to pull in a huge amount of events, very efficiently and analyze them later. Tokio is just one source of those events, but its a very important one.

Once we had Tokio, I realized we could also pull in lots of other sources as well; Linux kernel events, application events, tracing etc. etc.

Folks have already had good luck using dial9 to find tricky issues in prod.

Does anyone else find it incredibly ironic that this article summarizing the paper was obviously written with AI?

All the headings and bullets and phrases like "The findings are clear:" stick out like a sore thumb.

Re:Mechanical Watch: Exploded View on Sunday June 22, 2025 @11:53AM (#44347908)
perhaps you did not read the post—the author attempted layer-by-layer first but discovered it was impossible to get a smooth final result.

This is apparently a well known issue among people who create resin-cast structures.

Another useful library in this space that allows you to avoid manually writing bindings is https://github.com/duchess-rs/duchess
Re:The Cheating Device (ChatGPT on a TI-84) [video] on Thursday September 19, 2024 @08:57PM (#41597818)
TLDR: Install a wifi microcontroller _inside_ a TI-84. Make a little app that can talk to ChatGPT.
Re:AWS Libcrypto for Rust on Friday January 12, 2024 @09:47PM (#38976864)
How crazy is the build chain these days? Well, to build it in FIPS mode you need a Go compiler!
The verbatim responses come as part of "Browse with Bing" not the model actually verbatim repeating articles from training data. This seems pretty different and something actually addressable.

> the suit showed that Browse With Bing, a Microsoft search feature powered by ChatGPT, reproduced almost verbatim results from Wirecutter, The Times’s product review site. The text results from Bing, however, did not link to the Wirecutter article, and they stripped away the referral links in the text that Wirecutter uses to generate commissions from sales based on its recommendations.

Re:General Availability of the AWS SDK for Rust on Wednesday November 29, 2023 @10:35AM (#38460694)
The Rust SDK does not currently use the CRT under the hood. The CRT is a high performance C-Library for fast HTTP connections (and a lot more).

For S3, there is a meta-layer that interceps requests to S3 and converts them into ranged-gets and multipart uploads for parallelization.

It's quite complex and can also use significantly more memory, but it does allow for *much* faster uploads and downloads in some circumstances.

Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @01:07PM (#38448838)
Probably the biggest one is "batteries included but replaceable." The Rust ecosystem is still maturing, so we did a lot of work to make reasonable default choices but still allow customers to make different ones.

Some of our other design tenets are here: https://smithy-lang.github.io/smithy-rs/design/tenets.html

Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @12:50PM (#38448570)
It's on our radar—one of the biggest issues is that some of the services like EC2 are absolutely massive. We're investigating ways for customers to only compile the operations they need, etc.
Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @12:49PM (#38448566)
if you use other Async runtimes, you need to "wire them up", in this case by providing a "sleep" implementation. I'd strongly recommend using Tokio, especially if you're a beginner. I think the "beefy" statements are not necessarily accurate. You can use it as a single-threaded runtime if you want. Tokio is not going to have a significant impact on your compile times or binary size (given you're already using the SDK!)
Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @12:47PM (#38448536)
The Rust SDK is built on top of the smithy-rs code generator. On the service coverage front, you'll find nearly 100% parity—There are some legacy APIs that aren't supported. It also doesn't have many "high level libraries" (e.g. S3 transfer manager) that can find for other languages.

New services will come out the same day as all other SDKs–All SDKs utilize the same automated system to deploy new releases.

The only exception is services which require extensive custom code. We're still catching up on those for the Rust SDK.

Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @11:19AM (#38447388)
> 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

Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @11:01AM (#38447158)
Not all languages have a great interop story with Rust. Binding the JNI is especially tricky, for example. Furthermore, when performance isn't important, the need to package and compile Rust code may be an unnecessary hassle.
Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @10:59AM (#38447113)
Although this is true in theory, in practice you need to be very careful when writing code if you want to target WASM. One example: `SystemTime::now` will panic on some WASM platforms!
Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @10:57AM (#38447094)
Yep! There are actually examples that use Web Assembly: https://github.com/awslabs/aws-sdk-rust/tree/main/examples/w...
Re:General Availability of the AWS SDK for Rust on Tuesday November 28, 2023 @09:10AM (#38445830)
Hello! Me and some other folks who work on the Rust SDK will be around today answering questions in the comments.
Re:Git.io no longer accepts new URLs on Friday January 21, 2022 @11:48AM (#30026109)
Am I the only one who has never heard of nor seen a git.io shortened URL?
Re:Wordle Is a Love Story on Thursday January 06, 2022 @02:48PM (#29828940)
the optimal 5 letter starting work is SERAI (as computed by someone's AI)

Older »