Dusty Pomerleau
@dpom.bsky.social
Web hobbyist • Leptos, Axum, Gel
(he/him)
(he/him)
Reposted by Dusty Pomerleau
If you've ever used Rust, you've felt jyn's positive influence — even if you never realized it.
I hope my token of recognition is just the start of jyn's invaluable work getting the funding it deserves.
Folks, can we get jyn some more funding? RT 🙏
github.com/sponsors/jyn...
I hope my token of recognition is just the start of jyn's invaluable work getting the funding it deserves.
Folks, can we get jyn some more funding? RT 🙏
github.com/sponsors/jyn...
Sponsor @jyn514 on GitHub Sponsors
Support jyn's open source work on Rust, and their writing about a vision for the future of computers
github.com
November 30, 2025 at 3:51 PM
If you've ever used Rust, you've felt jyn's positive influence — even if you never realized it.
I hope my token of recognition is just the start of jyn's invaluable work getting the funding it deserves.
Folks, can we get jyn some more funding? RT 🙏
github.com/sponsors/jyn...
I hope my token of recognition is just the start of jyn's invaluable work getting the funding it deserves.
Folks, can we get jyn some more funding? RT 🙏
github.com/sponsors/jyn...
@vivaldi.com This issue where the address bar sends you to search instead of the site in question is happening again:
forum.vivaldi.net/topic/93512/...
The specific circumstance I'm seeing is when you enter a full URL path for a page within a `.au` TLD.
forum.vivaldi.net/topic/93512/...
The specific circumstance I'm seeing is when you enter a full URL path for a page within a `.au` TLD.
Direct URL input broken, goes to search results instead
@ImaginaryFreedom While I don't feel quite as dramatically as this, I do agree with you. The address bar is the main thing about Vivaldi that I hate, for thi...
forum.vivaldi.net
November 29, 2025 at 7:23 AM
@vivaldi.com This issue where the address bar sends you to search instead of the site in question is happening again:
forum.vivaldi.net/topic/93512/...
The specific circumstance I'm seeing is when you enter a full URL path for a page within a `.au` TLD.
forum.vivaldi.net/topic/93512/...
The specific circumstance I'm seeing is when you enter a full URL path for a page within a `.au` TLD.
Ah - it appears that declaring them brings them into scope when you import the derive macro. Makes sense in retrospect.
What is the purpose of declaring the namespace of derive macro helper attributes in #RustLang? Since you are parsing the helper attributes yourself, it seems like you can detect them either way. Is there a consequence to not declaring them?
November 29, 2025 at 7:17 AM
Ah - it appears that declaring them brings them into scope when you import the derive macro. Makes sense in retrospect.
I wish I had a better understanding of the approach the Snix team is taking to their Rust rewrite. When I look at the repo, I run across signatures like this, which I find terrifying. Do they need to do this for some sort of 1:1 compatibility with NixCPP?
![/// Interprets the given code snippet, printing out warnings and errors and returning the result
#[allow(clippy::too_many_arguments)]
pub fn evaluate<E: std::io::Write + Clone + Send>(
stderr: &mut E,
snix_store_io: Rc<SnixStoreIO>,
code: &str,
path: Option<PathBuf>,
args: &Args,
allow_incomplete: AllowIncomplete,
env: Option<&FxHashMap<SmolStr, Value>>,
globals: Option<Rc<GlobalsMap>>,
source_map: Option<SourceCode>,
) -> Result<EvalResult, IncompleteInput> {](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:zzrxayhe546tzprc2bbw3yls/bafkreig4cu225hviokl3jtt2jibbfpbaillwfuu3iqoogujvbk6xiyj7ly@jpeg)
November 28, 2025 at 11:24 PM
I wish I had a better understanding of the approach the Snix team is taking to their Rust rewrite. When I look at the repo, I run across signatures like this, which I find terrifying. Do they need to do this for some sort of 1:1 compatibility with NixCPP?
Every post to the default field values RFC makes me feel so happy. This is gonna be a huge ergonomic boost when it becomes widespread.
github.com/rust-lang/ru...
github.com/rust-lang/ru...
Tracking issue for RFC 3681: Default field values · Issue #132162 · rust-lang/rust
This is a tracking issue for the RFC "3681" (rust-lang/rfcs#3681). The feature gate for the issue is #![feature(default_field_values)]. Allow struct definitions to provide default values for indivi...
github.com
November 28, 2025 at 11:10 PM
Every post to the default field values RFC makes me feel so happy. This is gonna be a huge ergonomic boost when it becomes widespread.
github.com/rust-lang/ru...
github.com/rust-lang/ru...
@fasterthanli.me I've been following the work on Facet with interest, but I don't completely understand why Rust needs reflection. Is the main motivation to reduce compile times? What little I've read about reflection in other languages seems like it can be achieved at compile time with traits.
November 27, 2025 at 10:56 AM
@fasterthanli.me I've been following the work on Facet with interest, but I don't completely understand why Rust needs reflection. Is the main motivation to reduce compile times? What little I've read about reflection in other languages seems like it can be achieved at compile time with traits.
I find it baffling that GitHub enables CI workflows on every fork by default. For large repos forked by individual users, the CI inevitably fails over and over again. At GitHub scale, this must waste an astronomical amount of compute.
November 27, 2025 at 10:24 AM
I find it baffling that GitHub enables CI workflows on every fork by default. For large repos forked by individual users, the CI inevitably fails over and over again. At GitHub scale, this must waste an astronomical amount of compute.
What is the purpose of declaring the namespace of derive macro helper attributes in #RustLang? Since you are parsing the helper attributes yourself, it seems like you can detect them either way. Is there a consequence to not declaring them?
November 27, 2025 at 9:59 AM
What is the purpose of declaring the namespace of derive macro helper attributes in #RustLang? Since you are parsing the helper attributes yourself, it seems like you can detect them either way. Is there a consequence to not declaring them?
Reposted by Dusty Pomerleau
Manager: "What's this milestone 'Living on a prayer' ?"
Me: "That's the documentation deliverable."
Manager: "What's the status of that?"
Me: "We're halfway there"
Manager: "Why is progress so slow?"
Me: "You fired Tommy"
Manager: "So?"
Me: "Tommy used to work on the docs"
Me: "That's the documentation deliverable."
Manager: "What's the status of that?"
Me: "We're halfway there"
Manager: "Why is progress so slow?"
Me: "You fired Tommy"
Manager: "So?"
Me: "Tommy used to work on the docs"
February 23, 2025 at 9:12 PM
Manager: "What's this milestone 'Living on a prayer' ?"
Me: "That's the documentation deliverable."
Manager: "What's the status of that?"
Me: "We're halfway there"
Manager: "Why is progress so slow?"
Me: "You fired Tommy"
Manager: "So?"
Me: "Tommy used to work on the docs"
Me: "That's the documentation deliverable."
Manager: "What's the status of that?"
Me: "We're halfway there"
Manager: "Why is progress so slow?"
Me: "You fired Tommy"
Manager: "So?"
Me: "Tommy used to work on the docs"
Reposted by Dusty Pomerleau
My colleague just released a new error handling #crate for #rustlang called rootcause and it's quite neat! (although I haven't had a chance to play with it yet...): github.com/rootcause-rs...
There's also a bit of discussion happening here: old.reddit.com/r/rust/comme...
There's also a bit of discussion happening here: old.reddit.com/r/rust/comme...
GitHub - rootcause-rs/rootcause
Contribute to rootcause-rs/rootcause development by creating an account on GitHub.
github.com
November 26, 2025 at 2:55 AM
My colleague just released a new error handling #crate for #rustlang called rootcause and it's quite neat! (although I haven't had a chance to play with it yet...): github.com/rootcause-rs...
There's also a bit of discussion happening here: old.reddit.com/r/rust/comme...
There's also a bit of discussion happening here: old.reddit.com/r/rust/comme...
LLMs are just email all over again.
I am old enough to remember when email came out. It was really fun, and acted as both our social media and our messaging platform. It stopped being fun because it lowered the barrier for absolutely anyone to demand our time. LLMs have this same asymmetry.
I am old enough to remember when email came out. It was really fun, and acted as both our social media and our messaging platform. It stopped being fun because it lowered the barrier for absolutely anyone to demand our time. LLMs have this same asymmetry.
November 24, 2025 at 10:50 PM
LLMs are just email all over again.
I am old enough to remember when email came out. It was really fun, and acted as both our social media and our messaging platform. It stopped being fun because it lowered the barrier for absolutely anyone to demand our time. LLMs have this same asymmetry.
I am old enough to remember when email came out. It was really fun, and acted as both our social media and our messaging platform. It stopped being fun because it lowered the barrier for absolutely anyone to demand our time. LLMs have this same asymmetry.
Reposted by Dusty Pomerleau
Reading this made me want to walk into the sea
The comment thread here is the embodiment of :lolsob:
There is legitimate promise to LLM-assisted coding, but there are also legitimate risks. Like this. And no one here is malicious!
There is legitimate promise to LLM-assisted coding, but there are also legitimate risks. Like this. And no one here is malicious!
One of the many joys of using AI for programming is the creation of huge PRs on complex topics that the authors barely understand, but still suggest "because they work". Here's a great example from #OCaml github.com/ocaml/ocaml/...
Kudos to OCaml's maintainers for handling this so gracefully.
Kudos to OCaml's maintainers for handling this so gracefully.
November 24, 2025 at 9:33 PM
Reading this made me want to walk into the sea
Reposted by Dusty Pomerleau
Australia's Bureau of Meteorology got a new website recently which was initially announced to have cost $4.1 million AUD, but it came out yesterday that it in fact cost $96.5 million AUD!
$96.5 million AUD for a weather site redesign!
Here is the new site in question: www.bom.gov.au
$96.5 million AUD for a weather site redesign!
Here is the new site in question: www.bom.gov.au
www.bom.gov.au
November 24, 2025 at 5:26 AM
Australia's Bureau of Meteorology got a new website recently which was initially announced to have cost $4.1 million AUD, but it came out yesterday that it in fact cost $96.5 million AUD!
$96.5 million AUD for a weather site redesign!
Here is the new site in question: www.bom.gov.au
$96.5 million AUD for a weather site redesign!
Here is the new site in question: www.bom.gov.au
Reposted by Dusty Pomerleau
This feels like an extension/formalization of the ideas from this post greptime.com/blogs/2024-0.... I've implemented this in a large codebase and it works _really_ well, but there are some rough edge cases to work through. I'll definitely have to try this out in newer projects.
Error Handling for Large Rust Projects - Best Practice in GreptimeDB
How to handle and report errors effectively in Rust applications is a common question. This blog shares our experience organizing variant types of Error in a complex system like GreptimeDB, from how a...
greptime.com
November 23, 2025 at 10:10 AM
This feels like an extension/formalization of the ideas from this post greptime.com/blogs/2024-0.... I've implemented this in a large codebase and it works _really_ well, but there are some rough edge cases to work through. I'll definitely have to try this out in newer projects.
Reposted by Dusty Pomerleau
Turns out the TokenStream implementation of rust-analyzer's proc-macro server is super slow when it comes to one of the most common proc-macro operations: concatenation. I noticed that in Zed's codebase, there were ~4 derives that just straight up together took 8 seconds to expand in rust-analyzer.
November 22, 2025 at 4:20 PM
Turns out the TokenStream implementation of rust-analyzer's proc-macro server is super slow when it comes to one of the most common proc-macro operations: concatenation. I noticed that in Zed's codebase, there were ~4 derives that just straight up together took 8 seconds to expand in rust-analyzer.
nothin sounds quite
November 19, 2025 at 9:12 PM
nothin sounds quite
yolo()
yolo_cuz("i said so!")
yolo_cuz("i said so!")
#rustlang hot take: We should rename .unwrap() to .or_panic(). (And .expect() to .or_panic_with().) "Unwrap" is a terrible name for the panicking function, especially since we also have things like .unwrap_or() and .unwrap_or_default() which never panic.
November 19, 2025 at 8:59 PM
yolo()
yolo_cuz("i said so!")
yolo_cuz("i said so!")
Reposted by Dusty Pomerleau
#rustlang hot take: We should rename .unwrap() to .or_panic(). (And .expect() to .or_panic_with().) "Unwrap" is a terrible name for the panicking function, especially since we also have things like .unwrap_or() and .unwrap_or_default() which never panic.
November 19, 2025 at 7:32 AM
#rustlang hot take: We should rename .unwrap() to .or_panic(). (And .expect() to .or_panic_with().) "Unwrap" is a terrible name for the panicking function, especially since we also have things like .unwrap_or() and .unwrap_or_default() which never panic.
Reposted by Dusty Pomerleau
🦀 Bad news everyone - unwrap() is the reason behind cloudflare outage
>The FL2 Rust code that makes the check and was the source of the unhandled error is shown below
blog.cloudflare.com/18-november-...
#rustlang
>The FL2 Rust code that makes the check and was the source of the unhandled error is shown below
blog.cloudflare.com/18-november-...
#rustlang
Cloudflare outage on November 18, 2025
Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.
blog.cloudflare.com
November 19, 2025 at 3:11 AM
🦀 Bad news everyone - unwrap() is the reason behind cloudflare outage
>The FL2 Rust code that makes the check and was the source of the unhandled error is shown below
blog.cloudflare.com/18-november-...
#rustlang
>The FL2 Rust code that makes the check and was the source of the unhandled error is shown below
blog.cloudflare.com/18-november-...
#rustlang
Reposted by Dusty Pomerleau
It's time for the State of Rust Survey!
The Rust Project invites you to take this year’s survey, whether you have just begun using Rust, you consider yourself an intermediate to advanced user, or you have not yet used Rust but intend to one day 🦀
The Rust Project invites you to take this year’s survey, whether you have just begun using Rust, you consider yourself an intermediate to advanced user, or you have not yet used Rust but intend to one day 🦀
Launching the 2025 State of Rust Survey | Rust Blog
Empowering everyone to build reliable and efficient software.
blog.rust-lang.org
November 18, 2025 at 5:35 AM
It's time for the State of Rust Survey!
The Rust Project invites you to take this year’s survey, whether you have just begun using Rust, you consider yourself an intermediate to advanced user, or you have not yet used Rust but intend to one day 🦀
The Rust Project invites you to take this year’s survey, whether you have just begun using Rust, you consider yourself an intermediate to advanced user, or you have not yet used Rust but intend to one day 🦀
Reposted by Dusty Pomerleau
🦀 I've improved the implementation behind all the string formatting macros in Rust: println, panic, format, write, log::info, etc. (Everything using format_args!().) They will compile a bit faster, use a bit less memory while compiling, result in smaller binaries, and produce more efficient code! 🎉
November 13, 2025 at 1:31 PM
🦀 I've improved the implementation behind all the string formatting macros in Rust: println, panic, format, write, log::info, etc. (Everything using format_args!().) They will compile a bit faster, use a bit less memory while compiling, result in smaller binaries, and produce more efficient code! 🎉
Is this a ZST or a zen koan?
November 8, 2025 at 9:47 AM
Is this a ZST or a zen koan?
