My personal take on this, at least when dealing with more complex or production code:
Performance is not an issue with exceptions if you don't use them for control flow, they should be an unusual occurrence wherever possible.
If you expect to throw and later handle an exception regularly, I'd try to include relevant info about the failure in the returned value, or even better in the returned type, and skip throwing the exception altogether.
Returning a type that contains both error info and the actual result (if there is one) and forces the caller of your function to handle any contained error info before being able to access the actual result has the same effect as a try/catch block without the major performance implications.
This is basically what rust does everywhere in order to completely remove the concept of exceptions, but it's a nice performance optimization for langues with exceptions as well.
Exceptions should interrupt your programs flow, not control it, at least in all hot execution paths. Thanks for coming to my ted talk
I'm mostly checking if my standards have lowered since the last time I looked into the fridge
Doch, iReddit, und sie war eine Katastrophe. Hat anfangs sogar Geld gekostet.
Lustig, wo doch die offizielle Reddit-App auch ehemalig eine Drittanbieter-App war (Alien Blue), bis reddit sie gekauft hat weil deren eigene App so scheiße war.
Sich jetzt hinzustellen und zu sagen dass APIs gar nicht dafür da sind von einem client genutzt zu werden ist auch ein bisschen frech. Was, außer scraping, soll man denn damit sonst machen? lol