3 ms·
One things that came to mind when reading your comment was some of my frustration using OS X. When an app in OS X or OS X itself stops working you don't get a b
by kapnobatairza 14y ago
One things that came to mind when reading your comment was some of my frustration using OS X. When an app in OS X or OS X itself stops working you don't get a blue screen or a "this application has crashed" error - it just stops working. Many of my friends would have the false illusion that OS X is much more stable than Windows 7 because they see less error messages.
- stdbrouw 14y agoHmm, but you do always get an error message when you relaunch, allowing you to report the error or see some details.
- superuser2 14y agoI used to see the "spinning beachball of death" scenario every now and then, but on Lion and a 2011 Macbook Air I haven't once. Occasionally third party applications will exit and there will be a "____ has quit unexpectedly" message with an option to relaunch. Details are available in logfiles; anyone who has a use for those details most likely knows where to find them. The end user can't do anything with memory addresses, etc. so it makes sense that they don't seem them.
- kapnobatairza 14y agoOf course, Apple provides the details for those who care to look, just that it hides the information from the everyday user who doesn't want to. This is just a personal opinion, but just failing is probably less scary to the everyday user than being immediately presented with a bunch of error messages/a blue screen error message - even though they might mean the exactly the same thing.