---
title: "Comment by Julian on \"Stop catching errors in TypeScript; Use the Either type to make your code predictable\" | Hashnode"
description: "Thanks for writing this! I agree, especially the first part about not (ab)using exceptions to model expected outcomes of a function/process. Regarding the Eithe"
url: "https://hashnode.com/posts/stop-catching-errors-in-typescript-use-the-either-type-to-make-your-code-predictable/61740f980f452c1cd94fa17c/comment/6185448afd5d634d01698651"
---

[Discussion](https://hashnode.com/posts/stop-catching-errors-in-typescript-use-the-either-type-to-make-your-code-predictable/61740f980f452c1cd94fa17c)

Comment [Stop catching errors in TypeScript; Use the Either type to make your code predictable](https://hashnode.com/posts/stop-catching-errors-in-typescript-use-the-either-type-to-make-your-code-predictable/61740f980f452c1cd94fa17c)

[Julian](https://hashnode.com/@julianweb)

[Nov 5, 2021](https://hashnode.com/posts/stop-catching-errors-in-typescript-use-the-either-type-to-make-your-code-predictable/61740f980f452c1cd94fa17c/comment/6185448afd5d634d01698651)

Thanks for writing this! I agree, especially the first part about not (ab)using exceptions to model expected outcomes of a function/process.

Regarding the `Either<Left,Right>` approach. I'm not convinced. I can't find a compelling reason to prefer this over discriminated union types.

Perhaps you can think of an advantage?

Thanks again!