4 ms·
It's rather bloated, and constantly throws exceptions for control flow. It can be convenient, but it's not really worth it in my opinion.
by jrs95 9y ago
It's rather bloated, and constantly throws exceptions for control flow. It can be convenient, but it's not really worth it in my opinion.
- ddorian43 9y agoWhich is in your opinion ?
- jrs95 9y agoI guess it's all my opinion, other than exceptions for control flow. Set your debugger to pause on all exceptions and then hit a hello world endpoint...it's terrifying.
- le-mark 9y agoI sometimes see people object to exception based control as you do here. I get it; it's essentially goto in diguise. But I've never read anyone discuss the pros and cons, or definitively call it out for what it is. Do you have any references on this topic?
- peoplewindow 9y agoExceptions for control flow are a performance problem in most environments. The JVM does a good job of optimising exceptions very aggressively but throwing one is a relatively expensive operation if the JIT compiler wasn't able to fuse the throw/catch together. It's a bit weird to use exceptions for control flow for this reason.
- jrs95 9y agoI don't, but the when exceptions become the norm it makes debugging much more difficult. I'm not an expert on the subject, but it seems to have a negative impact on performance as well. And in the case of a simple web app, it just shouldn't be necessary. Maybe it makes sense for Spring to do it, but that would indicate that it's more complex than it needs to be.