3 ms·

But then, throwing exceptions instead of just crashing the app can also let tools like crashlytics get them and send them to a web service before the app really

• mikeash 11y ago
  Throwing an exception isn't really the problem, the problem is the catch-all exception handler in the event loop that just logs them and continues running the app. If that was gone, and NSAssert threw exceptions that by default crashed the app, that would be pretty much fine.
  • bsaul 11y ago
    Yeap, but that was also a point against using abort or exit functions in production code.
    • mikeash 11y ago
      Cleanly exiting is bad, but your crash reporting should catch abort().
• astrange 11y ago
  You can always catch regular crashes in your app through Mach exceptions, or by scanning the crash logs directory for your app.