.unwrap() always sounded odd to me. Maybe something like that could help projects? gist.github.com/jeromegn/9f0...

Always tempted by the poutine at the shawarma place, but too scared to get something subpar when I know the shawarma plate is so damn good

Looking good

Gotta keep the packets going through to keep it warm!

Holy shit. It was interesting to think about these things hypothetically, but now that it might be right around the corner… I don’t know what to think!

The Rust in Linux movement is getting immense pushback from the current maintainers. It takes a toll on all contributors. I wouldn’t put myself through that.

Huh, didn’t think the nova engine had so much implemented!

That does look nice. Also been using Iosevka for years. I’m not sure I could use a non-condensed font anymore.. saves so much width!

Rustconf when it was in Montreal (local to me) had special priced tickets for locals ($50 IIRC). There aren’t for Seattle?

Nice. Do you happen to know why it’s comparing to s3fs instead of something like juicefs, geesefs or tigrisfs? I assumed s3fs was antiquated and not used very much.

My first reaction is that it’s not really embedded if it uses Postgres :) but maybe a good Postgres setup is what’s expected. If it used SQLite or fjall or another embeddable DB, you could get rid of that dependency.

I’ve only discovered its existence this week and it’s solving a lot of problems for me. Previously tried axum+utoipa and dropshot. Both solutions had their own issues where poem seems to just work and be flexible enough for my needs!

If I understand correctly, their software requires generating Rust code from SQL. Instead of making it all one big crate, they splitted it into a ton of crates. They are not publishing the crates, they’re only generated at build-time for specific uses of Feldera