Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #7307

F

Flawless

Company blog · flawless.dev/essays · on HN as bkolobaraprogrammingsystems

Flawless is the company blog at flawless.dev, writing about programming and systems. Since 2023, 10 different Hacker News readers have linked it 15 times, most often “Flawless – Durable execution engine for Rust”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
15mentions?
10HN people?
2023–2026first – last linked?
Links on Hacker News per year · peak 6 in 2024

Too few sampled comments (7) to say how often HN recommends it.?

Why HN links it

HN readers link flawless.dev's essays, such as 'When letting it crash is not enough', which discuss durable execution beyond Erlang-style restarts, and compare it to similar workflow engines.

Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Flawless is an execution engine for durable computation. It will run your code until completion even in the presence of hardware or software failure.

The author on HN?

bkolobara · 1,361 karma · member since 2011

building lubeno.dev & flawless.dev

From their public HN profile, which links to this site.

Most-linked posts?

  1. Flawless – Durable execution engine for Rust
    7 people · 7 mentions · first linked 2023-10-25
  2. When "letting it crash" is not enough
    3 people · 3 mentions · first linked 2023-10-24
  3. Flawless Replay, time-traveling debugger for Rust workflows
    2 people · 2 mentions · first linked 2024-12-09

What Hacker News says?

  1. Ah this makes sense. I always thought "let it crash" made it sound like Elixir devs just don't bother with error checking, like writing Java without any `catch`es, or writing Rust that only uses `.unwrap()`. If they just mean "processes should be restartable" then that sounds way more reasonable. Similar idea to this but less fancy: https://flawless.dev/ It's a pretty terrible slogan if it makes your language sound…

    Comment linking /

    on “Don't “let it crash”, let it heal”
  2. Submitted When "letting it crash" is not enough as a story · 157 points

    HN discussion
  3. properly examined, this is another form of compilation, except slightly handicapped. i wonder if it would be possible to unroll/compile the function three-address code[0] style before execution, instead of the current model where you use specialized apis (eg temporal[1] and flawless[2]). i want to write my code like any program should be written, without special incantations, but still get durable execution as a non…

    Comment linking /

    on “When "letting it crash" is not enough”
  4. Submitted Flawless is now in public beta as a story · 39 points

    HN discussion
  5. The main page ( https://flawless.dev/ ) has a diagram/video that shows how it would work and it basically writes any 'side effects' to a log which is used to track their existence. If they exist in the log, you read them; if they don't you run the code that generates them and then log it. It's interesting, but I can't imagine how it is going to work at scale, both in terms of managing state across a very large appli…

    Comment linking /

    on “When "letting it crash" is not enough”
  6. Submitted Flawless Replay, time-traveling debugger for Rust workflows as a story · 5 points

    HN discussion
  7. I believe https://flawless.dev/ is another implementation with a very similar technology stack. I'd love to know how you compare and what the key differences are!

    Comment linking /

    on “Show HN: Obelisk – a WASM-based deterministic workflow engine”
  8. Submitted Rust Is Growing as a story · 2 points

    HN discussion
  9. Soon this will be open-source https://flawless.dev/

    Comment linking /

    on “Just Use Postgres for Durable Workflows”
  10. Submitted Flawless – Durable execution engine for Rust as a story · 2 points

    HN discussion
  11. First blog post mentions Erlang/OTP: https://flawless.dev/essays/when-letting-it-crash-is-not-eno...

    Comment linking /essays/when-letting-it-crash-is-not-enough/

    on “Flawless – Durable execution engine for Rust”
  12. Submitted Flawless Replay - time-travel debugger for Rust workflows as a story · 1 points

    HN discussion
  13. Thank you! I hand coded it with just HTML, CSS and JavaScript and put a lot of effort and love into it. The code is not the prettiest, but the implementation is straight forward if anyone wants to check it out https://flawless.dev/js/how-does-it-work-animation.js

    Comment linking /js/how-does-it-work-animation.js

    on “Flawless – Durable execution engine for Rust”
  14. Submitted When "letting it crash" is not enough as a story · 1 points

    HN discussion
  15. Been kicking around a similar idea in the back of my mind from the first moment "functional core / imperative shell" [0] and "sans-IO" [1] infected my brain. I've been chasing that high ever since. Unfortunately, whenever I try to apply this pattern 100%, I hit all kinds of walls: language isn't expressive enough to support what I want; the amount of wiring/glue to support it becomes a burden; the resulting code is…

    Comment linking /

    on “Show HN: Pure Effect – Reproduce production bugs on your laptop without a DB”

Search all of HN for flawless.dev

Linked by the same people?