The point here is not how to protect users from uncaught exception. It is more like: how to make a developer’s life easier, in a world where unpredictable exceptions occur on a daily basis, while developing…
But I see your point: you mean that by putting the “main loop” inside try/catch should catch most of the exceptions and exit gracefully?
Ok, I accept it, but still I wonder what would happen if some exception take place inside another thread (e.g. some http stuff…)
And from a Jogl developer standpoint, it is strange at the first place that cmd-Q cease to work at some point.
Could it be related to the way LWJGL treats full-screen windows on OSX? (and to the point that no “system overlays” appear on top of the screen, e.g. when changing the Mac’s volume?..)