So happy to hear you've finally warmed up to rust :P

Small PSA: At n0 we've seen flume lose notifications when you cancel its async receive futures, so it's not fully cancel-safe.

See the PR description in github.com/n0-computer/...

YES! I literally called it "weird week" at fission.

And then I realized sometimes it's two weeks or more 😅

BANANA!

(I had a thing when I was visiting Vancouver Island of shouting banana every time I saw one of those slugs :D)

Maybe because productivity software is sold to enterprises, and enterprises care less about usability than end consumers, and end consumers consume on mobile mostly.

Also, I think there is UI/UX innovation I think, but it's all happening inside the browser.

Sounds similar to jodel.com/en/ which is quite successful in Germany.

(But also it tries to be anonymous. Makes sense if you want people to engage more.)

So yeah I agree this might work quite well.
If it's something that *should* be built - meh I'm not sure

It is so, so incredibly bad.

When it started auto-translating voices in the video with weird af robots as well... Man.

I mean, yay to making content accessible to a wider audience in the future, but it *really* doesn't work at the moment.

(German here)

Interestingly, Claude seems to be able to print an em dash, but not those fancy tilted quotation marks (they're called left and right double quotation marks apparently).

Also it seems to be unaware of that fact.

Wait. You're not claiming to have written this article or are you? That'd be @inanna.recursion.wtf I thought

Then use the type Vec<Box<dyn MyTrait>> for your Vec.

If you struggle to find the operations you want to list in the trait, you can survey the types you have and see if there's common functionality/fns with similar signatures that could changed to have the same signature.

The trait option:
You take a survey of the operations/fns you want to do on the elements of the vec, then encapsulate those in a trait and implement it on all the types you want to put into your Vec.
Make sure to only write fns that take &self or &mut self to keep your trait "dyn compatible".

The enum option:
You take a survey of all types you need to store in the same Vec, make one enum out of them with a case for each type, then you look at usage of the vector and either pattern match on entries when you act on them, or encapsulate the pattern match in an fn on the enum itself.

Great question!
Generally two options:
1. An Enum
2. A Trait

Cont...