Now that I got your attention, let me specify what this article actually wants to say: STOP THROWING EXCEPTIONS! In the world of Kotlin, there are some great ways to catch exceptions. The most…

Pand's Blog provides developers with tutorials, tips, and insights on web development, frontend technologies, and software engineering practices. Developers can learn about modern web development frameworks, frontend build tools, and responsive design techniques, as well as explore tutorials on JavaScript libraries and CSS frameworks. Additionally, the blog covers topics such as web accessibility, performance optimization, and user experience design, empowering developers to create intuitive and accessible web applications.

ProAndroidDev

In Kotlin, it's recommended to avoid throwing exceptions and instead handle error scenarios using try/catch expressions, result objects, and functional programming paradigms. The default usage of try/catch is criticized for reducing readability and maintainability. The post suggests Kotlin's built-in Result class for better error handling, providing examples of how to wrap operations in Result objects and handle errors more effectively. This approach promotes cleaner, more testable code without relying on exceptions.

Stop throwing exceptions!

Nah, continue throwing Exceptions, it’s great.

AFAIK one of the reasons exceptions have been created is to overcome the cumbersome “if (success)” pattern, and they are widely used also in “non error” scenarios when some condition occurs preventing the following code to go on with its work.
I don’t find the suggested approach an ideal way to handle exceptions, replacing them with the good old “result code”, nor the tip to wrap all the methods that potentially throw exceptions into “catch adapters” feels like a good solution (you will find yourself with tons and tons of these methods).
Sorry but I think I’ll stick with exceptions. :-)

Yeah some devs are on one end of the spectrum, i.e. they abuse exceptions, but please don’t shift to the other extreme by never throwing exceptions when it makes sense to throw them. Exceptions have their place.

I also think that exceptions is the way (cf. comment above).
Nevertheless, this post makes me think that the author has a point. Somehow, throwed exceptions could appear in typing and make things clearer, yet probably too verbose.