The core idea behind it has to do with the fact that modern applications have a huge number of states that they can find themselves in. Eventually it becomes impossible for developers to predict all combinations of state that these variables will form.
neverthrow
supermacro • Updated 2026 Mar 23 14:43
proposal-try-operator
arthurfiorette • Updated 2026 Mar 20 9:8
The most important function in my codebase
Error handling in TypeScript is bad. Try catch is NOT a good pattern. Go got a lot wrong, but returning errors as values was absolutely right.
Thank you CodeRabbit for sponsoring! Check them out at: https://soydev.link/coderabbit
SOURCES
https://gist.github.com/t3dotgg/a486c4ae66d32bf17c09c73609dacc5b
https://github.com/supermacro/neverthrow
https://effect.website/
https://ethanniser.dev/blog/the-truth-about-effect/
Try T3 Chat? https://soydev.link/chat
Want to sponsor a video? Learn more here: https://soydev.link/sponsor-me
Check out my Twitch, Twitter, Discord more at https://t3.gg
S/O Ph4se0n3 for the awesome edit 🙏
https://www.youtube.com/watch?v=Y6jT-IkV0VM

When "letting it crash" is not enough
This essay explores the connection between Erlang's process supervision, state management and durable execution.
https://flawless.dev/essays/when-letting-it-crash-is-not-enough


Seonglae Cho