#asyncrust — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #asyncrust, aggregated by home.social.
-
🚀 Yawn-inducing nerd-fest alert! It's the ultimate showdown between Async Rust and #C #RTOS on an #STM32F446 #microcontroller. Spoiler: reading this is as exciting as watching paint dry, but with more acronyms and fewer laughs. 🤖🎨
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/ #AsyncRust #TechShowdown #NerdFest #HackerNews #ngated -
🚀 Yawn-inducing nerd-fest alert! It's the ultimate showdown between Async Rust and #C #RTOS on an #STM32F446 #microcontroller. Spoiler: reading this is as exciting as watching paint dry, but with more acronyms and fewer laughs. 🤖🎨
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/ #AsyncRust #TechShowdown #NerdFest #HackerNews #ngated -
🚀 Yawn-inducing nerd-fest alert! It's the ultimate showdown between Async Rust and #C #RTOS on an #STM32F446 #microcontroller. Spoiler: reading this is as exciting as watching paint dry, but with more acronyms and fewer laughs. 🤖🎨
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/ #AsyncRust #TechShowdown #NerdFest #HackerNews #ngated -
🚀 Yawn-inducing nerd-fest alert! It's the ultimate showdown between Async Rust and #C #RTOS on an #STM32F446 #microcontroller. Spoiler: reading this is as exciting as watching paint dry, but with more acronyms and fewer laughs. 🤖🎨
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/ #AsyncRust #TechShowdown #NerdFest #HackerNews #ngated -
🚀 Yawn-inducing nerd-fest alert! It's the ultimate showdown between Async Rust and #C #RTOS on an #STM32F446 #microcontroller. Spoiler: reading this is as exciting as watching paint dry, but with more acronyms and fewer laughs. 🤖🎨
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/ #AsyncRust #TechShowdown #NerdFest #HackerNews #ngated -
Embedded Rust RTOS vs. C RTOS
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
Comments: https://news.ycombinator.com/item?id=49540415
#HackerNews #EmbeddedRust #C #RTOS #RTOSComparison #AsyncRust #TechTrends
-
Embedded Rust RTOS vs. C RTOS
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
Comments: https://news.ycombinator.com/item?id=49540415
#HackerNews #EmbeddedRust #C #RTOS #RTOSComparison #AsyncRust #TechTrends
-
Embedded Rust RTOS vs. C RTOS
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
Comments: https://news.ycombinator.com/item?id=49540415
#HackerNews #EmbeddedRust #C #RTOS #RTOSComparison #AsyncRust #TechTrends
-
Embedded Rust RTOS vs. C RTOS
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
Comments: https://news.ycombinator.com/item?id=49540415
#HackerNews #EmbeddedRust #C #RTOS #RTOSComparison #AsyncRust #TechTrends
-
Embedded Rust RTOS vs. C RTOS
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
Comments: https://news.ycombinator.com/item?id=49540415
#HackerNews #EmbeddedRust #C #RTOS #RTOSComparison #AsyncRust #TechTrends
-
heyyy uuuhh if anyone knows how to implement a zero copy streaming parser (objects yielded would be a struct with Cow<'_,str> fields) with tokio-util codec crate hmu cos I can't figure it out lol
basically same issue as here, with no answers:
https://users.rust-lang.org/t/design-problem-minimizing-allocation-copying-while-parsing-for-a-tokio-decoder/11538
#rust #tokio #asyncRust -
heyyy uuuhh if anyone knows how to implement a zero copy streaming parser (objects yielded would be a struct with Cow<'_,str> fields) with tokio-util codec crate hmu cos I can't figure it out lol
basically same issue as here, with no answers:
https://users.rust-lang.org/t/design-problem-minimizing-allocation-copying-while-parsing-for-a-tokio-decoder/11538
#rust #tokio #asyncRust -
heyyy uuuhh if anyone knows how to implement a zero copy streaming parser (objects yielded would be a struct with Cow<'_,str> fields) with tokio-util codec crate hmu cos I can't figure it out lol
basically same issue as here, with no answers:
https://users.rust-lang.org/t/design-problem-minimizing-allocation-copying-while-parsing-for-a-tokio-decoder/11538
#rust #tokio #asyncRust -
heyyy uuuhh if anyone knows how to implement a zero copy streaming parser (objects yielded would be a struct with Cow<'_,str> fields) with tokio-util codec crate hmu cos I can't figure it out lol
basically same issue as here, with no answers:
https://users.rust-lang.org/t/design-problem-minimizing-allocation-copying-while-parsing-for-a-tokio-decoder/11538
#rust #tokio #asyncRust -
heyyy uuuhh if anyone knows how to implement a zero copy streaming parser (objects yielded would be a struct with Cow<'_,str> fields) with tokio-util codec crate hmu cos I can't figure it out lol
basically same issue as here, with no answers:
https://users.rust-lang.org/t/design-problem-minimizing-allocation-copying-while-parsing-for-a-tokio-decoder/11538
#rust #tokio #asyncRust -
Building on FUSE in Rust tends to involve a lot of boilerplate. libfuse-fs is an attempt to change that - trait-based abstractions, async I/O, overlay and passthrough support out of the box.
At Oxidize 2026, Ruiji Yu (Nanjing University) covers the design and lessons from real integrations: monorepo access and container image building.
🔗 https://oxidizeconf.com/sessions/libfuse_fs_a_ready_to_use_filesystem_library_based_on_fuse
#Oxidize2026 #RustLang #FUSE #Filesystem #AsyncRust #SystemsProgramming
-
Building on FUSE in Rust tends to involve a lot of boilerplate. libfuse-fs is an attempt to change that - trait-based abstractions, async I/O, overlay and passthrough support out of the box.
At Oxidize 2026, Ruiji Yu (Nanjing University) covers the design and lessons from real integrations: monorepo access and container image building.
🔗 https://oxidizeconf.com/sessions/libfuse_fs_a_ready_to_use_filesystem_library_based_on_fuse
#Oxidize2026 #RustLang #FUSE #Filesystem #AsyncRust #SystemsProgramming
-
Building on FUSE in Rust tends to involve a lot of boilerplate. libfuse-fs is an attempt to change that - trait-based abstractions, async I/O, overlay and passthrough support out of the box.
At Oxidize 2026, Ruiji Yu (Nanjing University) covers the design and lessons from real integrations: monorepo access and container image building.
🔗 https://oxidizeconf.com/sessions/libfuse_fs_a_ready_to_use_filesystem_library_based_on_fuse
#Oxidize2026 #RustLang #FUSE #Filesystem #AsyncRust #SystemsProgramming
-
Building on FUSE in Rust tends to involve a lot of boilerplate. libfuse-fs is an attempt to change that - trait-based abstractions, async I/O, overlay and passthrough support out of the box.
At Oxidize 2026, Ruiji Yu (Nanjing University) covers the design and lessons from real integrations: monorepo access and container image building.
🔗 https://oxidizeconf.com/sessions/libfuse_fs_a_ready_to_use_filesystem_library_based_on_fuse
#Oxidize2026 #RustLang #FUSE #Filesystem #AsyncRust #SystemsProgramming
-
@walterjizz IMO, message passing concurrency is way more flexible in the long run, so I'd go with that.
@PuercoPop Newer versions of tokio now come with a LocalRuntime, which allows spawning of !Send + !Sync Futures (unfortunately, they still need to be 'static, though😐):
https://docs.rs/tokio/latest/tokio/runtime/struct.LocalRuntime.html#method.spawn_localI'm probably biased, but I really like smol, because it is very flexible, e.g. your Futures don't even need to be 'static:
https://docs.rs/smol/latest/smol/struct.LocalExecutor.html#method.spawn -
@walterjizz IMO, message passing concurrency is way more flexible in the long run, so I'd go with that.
@PuercoPop Newer versions of tokio now come with a LocalRuntime, which allows spawning of !Send + !Sync Futures (unfortunately, they still need to be 'static, though😐):
https://docs.rs/tokio/latest/tokio/runtime/struct.LocalRuntime.html#method.spawn_localI'm probably biased, but I really like smol, because it is very flexible, e.g. your Futures don't even need to be 'static:
https://docs.rs/smol/latest/smol/struct.LocalExecutor.html#method.spawn -
@walterjizz IMO, message passing concurrency is way more flexible in the long run, so I'd go with that.
@PuercoPop Newer versions of tokio now come with a LocalRuntime, which allows spawning of !Send + !Sync Futures (unfortunately, they still need to be 'static, though😐):
https://docs.rs/tokio/latest/tokio/runtime/struct.LocalRuntime.html#method.spawn_localI'm probably biased, but I really like smol, because it is very flexible, e.g. your Futures don't even need to be 'static:
https://docs.rs/smol/latest/smol/struct.LocalExecutor.html#method.spawn -
@walterjizz IMO, message passing concurrency is way more flexible in the long run, so I'd go with that.
@PuercoPop Newer versions of tokio now come with a LocalRuntime, which allows spawning of !Send + !Sync Futures (unfortunately, they still need to be 'static, though😐):
https://docs.rs/tokio/latest/tokio/runtime/struct.LocalRuntime.html#method.spawn_localI'm probably biased, but I really like smol, because it is very flexible, e.g. your Futures don't even need to be 'static:
https://docs.rs/smol/latest/smol/struct.LocalExecutor.html#method.spawn -
@walterjizz IMO, message passing concurrency is way more flexible in the long run, so I'd go with that.
@PuercoPop Newer versions of tokio now come with a LocalRuntime, which allows spawning of !Send + !Sync Futures (unfortunately, they still need to be 'static, though😐):
https://docs.rs/tokio/latest/tokio/runtime/struct.LocalRuntime.html#method.spawn_localI'm probably biased, but I really like smol, because it is very flexible, e.g. your Futures don't even need to be 'static:
https://docs.rs/smol/latest/smol/struct.LocalExecutor.html#method.spawn -
Fuzzing finds bugs in Rust code - reliably so. But async Rust has largely stayed out of reach with its complexity making it hard for fuzzers to explore meaningfully.
At Oxidize 2026, Morgan Hill (@pcwizz) walks through what it takes to actually fuzz async Rust: the naive approaches that don't work, and an involved technique that does - involving LibAFL, user mode QEMU, and a fair amount of head scratching.
🔗 https://oxidizeconf.com/sessions/awaiting_exploitation
#Oxidize2026 #RustLang #Fuzzing #SecurityResearch #AsyncRust
-
Fuzzing finds bugs in Rust code - reliably so. But async Rust has largely stayed out of reach with its complexity making it hard for fuzzers to explore meaningfully.
At Oxidize 2026, Morgan Hill (@pcwizz) walks through what it takes to actually fuzz async Rust: the naive approaches that don't work, and an involved technique that does - involving LibAFL, user mode QEMU, and a fair amount of head scratching.
🔗 https://oxidizeconf.com/sessions/awaiting_exploitation
#Oxidize2026 #RustLang #Fuzzing #SecurityResearch #AsyncRust
-
Fuzzing finds bugs in Rust code - reliably so. But async Rust has largely stayed out of reach with its complexity making it hard for fuzzers to explore meaningfully.
At Oxidize 2026, Morgan Hill (@pcwizz) walks through what it takes to actually fuzz async Rust: the naive approaches that don't work, and an involved technique that does - involving LibAFL, user mode QEMU, and a fair amount of head scratching.
🔗 https://oxidizeconf.com/sessions/awaiting_exploitation
#Oxidize2026 #RustLang #Fuzzing #SecurityResearch #AsyncRust
-
Fuzzing finds bugs in Rust code - reliably so. But async Rust has largely stayed out of reach with its complexity making it hard for fuzzers to explore meaningfully.
At Oxidize 2026, Morgan Hill (@pcwizz) walks through what it takes to actually fuzz async Rust: the naive approaches that don't work, and an involved technique that does - involving LibAFL, user mode QEMU, and a fair amount of head scratching.
🔗 https://oxidizeconf.com/sessions/awaiting_exploitation
#Oxidize2026 #RustLang #Fuzzing #SecurityResearch #AsyncRust
-
Fuzzing finds bugs in Rust code - reliably so. But async Rust has largely stayed out of reach with its complexity making it hard for fuzzers to explore meaningfully.
At Oxidize 2026, Morgan Hill (@pcwizz) walks through what it takes to actually fuzz async Rust: the naive approaches that don't work, and an involved technique that does - involving LibAFL, user mode QEMU, and a fair amount of head scratching.
🔗 https://oxidizeconf.com/sessions/awaiting_exploitation
#Oxidize2026 #RustLang #Fuzzing #SecurityResearch #AsyncRust
-
UwU - There is a new #Rust #book #bundle over at #HumbleBooksBundle :awesome:
https://www.humblebundle.com/books/rust-systems-programming-bundle-books
Amongst others, it contains the excellent "Asynchronous Programming in Rust" book by Carl Fredrik Samson, which I can highly recommend! 👍
-
UwU - There is a new #Rust #book #bundle over at #HumbleBooksBundle :awesome:
https://www.humblebundle.com/books/rust-systems-programming-bundle-books
Amongst others, it contains the excellent "Asynchronous Programming in Rust" book by Carl Fredrik Samson, which I can highly recommend! 👍
-
UwU - There is a new #Rust #book #bundle over at #HumbleBooksBundle :awesome:
https://www.humblebundle.com/books/rust-systems-programming-bundle-books
Amongst others, it contains the excellent "Asynchronous Programming in Rust" book by Carl Fredrik Samson, which I can highly recommend! 👍
-
UwU - There is a new #Rust #book #bundle over at #HumbleBooksBundle :awesome:
https://www.humblebundle.com/books/rust-systems-programming-bundle-books
Amongst others, it contains the excellent "Asynchronous Programming in Rust" book by Carl Fredrik Samson, which I can highly recommend! 👍
-
UwU - There is a new #Rust #book #bundle over at #HumbleBooksBundle :awesome:
https://www.humblebundle.com/books/rust-systems-programming-bundle-books
Amongst others, it contains the excellent "Asynchronous Programming in Rust" book by Carl Fredrik Samson, which I can highly recommend! 👍
-
The promise of Async Rust often clashes with its current reality. This article argues that despite its potential, Async Rust remains in an MVP state, creating a 'two-tiered ecosystem' for developers. It highlights how Tokio's monoculture and the `Send + 'static` trap introduce significant complexity and overhead, often making traditional threading a more ergonomic and performant choice for common…
🤖 This post was AI-generated.
-
🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated -
🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated -
🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated -
🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated -
🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated -
Tokio!
It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.
People should use `smol` more - here's why:
#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:
https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/
-
Tokio!
It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.
People should use `smol` more - here's why:
#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:
https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/
-
Tokio!
It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.
People should use `smol` more - here's why:
#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:
https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/
-
Tokio!
It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.
People should use `smol` more - here's why:
#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:
https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/
-
Tokio!
It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.
People should use `smol` more - here's why:
#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:
https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/
-
🚀✨ RustConf 2025: where we learn that "cancelling" async Rust is as easy as cancelling your gym membership—good luck with that! The article promises a thrilling ride through the labyrinth of #programming jargon, complete with links nobody asked for and slides only a mother could love. 🎢🗣️
https://sunshowers.io/posts/cancelling-async-rust/ #RustConf2025 #asyncRust #humor #techcommunity #HackerNews #ngated -
🚀✨ RustConf 2025: where we learn that "cancelling" async Rust is as easy as cancelling your gym membership—good luck with that! The article promises a thrilling ride through the labyrinth of #programming jargon, complete with links nobody asked for and slides only a mother could love. 🎢🗣️
https://sunshowers.io/posts/cancelling-async-rust/ #RustConf2025 #asyncRust #humor #techcommunity #HackerNews #ngated -
🚀✨ RustConf 2025: where we learn that "cancelling" async Rust is as easy as cancelling your gym membership—good luck with that! The article promises a thrilling ride through the labyrinth of #programming jargon, complete with links nobody asked for and slides only a mother could love. 🎢🗣️
https://sunshowers.io/posts/cancelling-async-rust/ #RustConf2025 #asyncRust #humor #techcommunity #HackerNews #ngated -
🚀✨ RustConf 2025: where we learn that "cancelling" async Rust is as easy as cancelling your gym membership—good luck with that! The article promises a thrilling ride through the labyrinth of #programming jargon, complete with links nobody asked for and slides only a mother could love. 🎢🗣️
https://sunshowers.io/posts/cancelling-async-rust/ #RustConf2025 #asyncRust #humor #techcommunity #HackerNews #ngated -
Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓
Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.
1/?
-
Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓
Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.
1/?
-
Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓
Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.
1/?
-
Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓
Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.
1/?
-
Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓
Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.
1/?
-
Hey #Rust,
how dare you look so elegant as a systems programming language! 💅