CedarDB is a relational-first database that supports all your workloads, from transactional to analytical to graph, accessible through PostgreSQL's tools and SQL dialect.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

The post discusses the preference for exceptions over error values in error handling, arguing that exceptions are easier to work with, result in better user-facing error messages, and are more performant. It compares functional-style error reporting in languages like Go and Rust with traditional exception handling in languages like C++ and mentions that explicit error handling can often lead to verbose and less efficient code.

Why I Prefer Exceptions to Error Values

Throwing Exceptions Used to Be Terribly Slow

like everything in life it is a tradeoff.
In places where you expect errors and know how to handle them none of his arguments apply error values are faster. Throwing and catching an exception is terrifying slow, while a simple option type on the stack creates almost no overhead. Additionally I find switch expressions way simpler to read and maintain than try-catch blocks.
In cases where errors are truly exceptional an exception is the simpler option.
In cases where you need an error message you can just use a string as error type.
Choosing the right tool for the right exercise is the key to good code.

From my experience, as soon as you work with several people, exceptions are a problem because there is always at least one person who does not handle unsigned exceptions …
Moreover, if you follow good practices, you are supposed to handle exceptions by type, and therefore avoid a global try/catch in the main function.
Apart from ultra specific applications that require performance, the difference in execution speed between exception handling or error handling by call return is not significant.
In short, from my point of view I prefer 100 times over not to use exceptions, and when I use a language that does not handle the result like rist or equivalent, I make sure to implement it myself