While I appreciated neverthrow's explicit error handling model, I ran into a few issues:

- It's not actively maintained (many PRs left open)

- It requires different APIs for sync and async results

- It's class-based, making results harder to serialize

byethrow takes a different approach:

- Plain-object based (no classes)

- Unified API for both sync and async values

- Tree-shakable and minimal

- No third-party dependencies

I'd love feedback—especially from other TS developers who've used neverthrow, fp-ts, or similar libraries!