yosh

isntitvacant, 2 months ago to random

A jetlagged, maybe-silly thought: what if, instead of defining a language to compose wasm components (as in WAC), we took a page from pulumi/terraform CDK and exposed wasm component composition as a set of javascript APIs

yosh, 2 months ago to random

@fasterthanlime hey what’s that application called again you use to edit your scripts in? I remember it looked pretty neat, but I don't remember what it's called.

yosh, 2 months ago to random

I too have discovered balantro oh no

yosh, 2 months ago to random

LRT: wooh, the Rust compiler has apparently improved compile speeds by nearly 40% since 2020, as measured on Linux. That’s actually incredible!

yosh, 2 months ago to random

Wrote a few words on how we could adapt the async let syntax introduced in Swift SE-0304 to async Rust. But rather than using tasks, we could lower them to just futures and futures-concurrency.

I've include an example of how we'd write this today; and tbh - it's kind of convinced me we should maybe look into this more seriously, sooner. (Known unknown: I don't know whether the compiler can access the control flow graph soon enough to insert the right rewrite rules)

https://github.com/rust-lang/keyword-generics-initiative/blob/15c0fe4d5a367ab13c178290e5367989918c546f/evaluation/auto-concurrency.md

yosh, 2 months ago to random

I was talking with TC from WG Async yesterday, and I think we arrived at a useful framing for cancellation in async Rust: we should treat it nearly identically to panic.

A panic is an exceptional state in Rust: you can usually catch it, but when you do you probably want to to treat all resources in the panic's blast zone as poisoned, and usually discard them. You don't, and I repeat - do not - use panic as a primary control-flow mechanism in Rust. And the same applies to async cancellation.

yosh, 2 months ago to random

I’m out here writing async runtimes again like it’s 2019 — very pleased that I somehow still got it, hehe

yosh, 3 months ago to random

I just compiled and published a list of national Covid wastewater dashboards!

https://github.com/yoshuawuyts/covid-wastewater-dashboards

These can be pretty tricky to find; so I figured I should make a list of the ones I know of. If you know of any not on this list, please let me know or file a PR.

yosh, 3 months ago to random

@jer what’s your crate called again which makes everything scream if you LD_PRELOAD it? It’s the best and I want to reference it in a demo :P

thejpster, 3 months ago to random

Idle thought: what if in Rust you were able to write:

pub nopanic fn foo() { … }

Functions marked nopanic can only perform operations that are themselves nopanic. A bit like const fns. If you really wanted you could make main a nopanic function. Unchecked arithmetic and slicing, and functions like unwrap, would all be forbidden inside a nopanic function.

You could also use the keyword “safe” instead of “nopanic”, leaving the default to be ?safe, or semi-safe (no UB, but could panic).

yosh, 3 months ago to random

Async closures are finally available on nightly Rust! To celebrate I spent 30 mins today hacking together a semantically correct implementation of async Iterator::filter: https://github.com/yoshuawuyts/async-iterator/pull/5

This can actually borrow items in async closures; which is something that wasn't possible before. But also: check out how cool those bounds are!

whitequark, 3 months ago to random

I'm now officially a Bytecode Alliance Recognized Contributor 😊

I'm looking forward to many more years of fruitful collaboration and beautiful sociotechnical projects

yosh, 3 months ago to random

One of the worst, but imo solvable, aspects of email is that "reply" and "reply all" are both presented as equivalent options - and yet 99% of the time "reply all" is what you want to be doing.

It's either you want to reply to the thread ("reply all”), or you want to reply but modify the list of participants (“reply all” + edit recipients). "reply" is so rarely the right action, I don't understand why it is featured so prominently. Imo it really shouldn’t be.

yosh, 3 months ago to random

Just saw an ad for consultations with calligraphers to help you make cooler signatures. And like, that seems pretty fun?

There’s some security risk to that, but I feel like, signatures aren’t particularly trusted anymore anyway?

yosh, 3 months ago to random

New blog post: Extending Rust's Effect System

It's a transcript of the talk I gave last year at RustConf. I'm excited the videos are finally online so I can post this! This took me so many hours to put together; I hope people will enjoy it!

https://blog.yoshuawuyts.com/extending-rusts-effect-system/

xgranade, 3 months ago to random

You know what I miss? Video players. Not like a Netflix player, a Disney+ player, a YouTube player, a Crunchyroll player, a Hulu player....

Something where the interface is focused around playing videos and not around consuming a specific subscription. It was never the case with DVDs that the pause button moved around or worked differently depending on the movie studio that published a DVD.

yosh, 3 months ago to random

So you know the term “headless browser” which is a browser without a front end?

What would you call the opposite of that? Like a bodyless browser? For things which don’t actually contain the main thing, but only things like metadata. Like an HTTP request without a payload. Or a type system without runtime semantics?

yosh, 3 months ago to random

Not that anyone asked but: I don’t have a Bluesky account. I have no intention of creating one either. Despite some of the folks working on the protocol being former colleagues and are generally quite lovely.

I view Bluesky as Twitter all over again. Someone needs to pay for all the video and images to be hosted. That bill is not being footed by the users of Bluesky, but by venture capital firms. So we need to ask: what is the plan for when Bluesky inevitably needs to start generating money?

yosh, 3 months ago to random

It’s fun to see folks in th Rust community discover sans-io style libraries. Once you get the hang of it, I’ve found it often segues to thinking about capabilities as well.

I co-authored an entire sans-io HTTP stack a few years ago: https://blog.yoshuawuyts.com/async-http/ — I believe we had like, one piece of IO squirreled away there to handle HTTP timeouts correctly, and never quite got around to fixing it. But largely I believe this is the way we should be authoring our protocol libraries.