The blog post is proposing exceptions in the context of an MVC style app where the code that throws the exceptions is part of a request pipeline that also has a

The blog post is proposing exceptions in the context of an MVC style app where the code that throws the exceptions is part of a request pipeline that also has a global exception handler. This handler would be capable of logging and translating the typed exception to some acceptable output to the consumer. It seems most people arguing against this clearly didn't read the post or they don't understand the context and are giving their opinions on exceptions in general. The crux of the post is to leverage the fact that your controller code (in typical modern MVC frameworks) doesn't run in a vacuum, to reduce a lot of boilerplate/repetion around error handling.