Flawless is now publicly available for everyone to try it out. Check out the docs to get started! flawless.dev/docs/

Introduction

Introduction to durable execution with flawless.

My favorite "decl macro" shape is "markdown table". It's perfect for data like this. Also this is my "ORM" for fjall, the key + value types are used to bind the postcard ser/de code.

Twitter punishing posts that contain links just pushes everyone to do weird workarounds. People screenshot the link content and say "link in replay" or something similar. Such a fundamental feature of the internet is made into an inconvenience.

The Helix editor (written in Rust) added Scheme for their plugin system. It looks like an obvious mistake to me to not just go with Rust/Wasm and not force another language on contributors.

This really didn't need to be an app. A link to the wallpaper in the video comment would have solved the issue for 99% of people.

For some reason, this is the aesthetic my brain prefers. Is there a modern take on this?

Developers: I like to split my contributions into small atomic commits. Me:

It's freezing in the co-working space. Even the Rust compiler can't keep me warm.

The only rule I constantly follow in my codebases is the "optimize for rewrites" rule. No matter how good the initial design is, once you write the thing, you will have a much better idea of what you actually need. No need to lock yourself into a specific architecture/design.

There is no better feeling when refactoring some Rust code and the compiler goes: "can't let you do this, in a completely different file the closure captures something that is not Sync and it would cause a race condition if you send this to another thread". Rust always has your back!