3 ms·
> The beachball on OSX frequently causes the whole UI shell to freeze solid. The beachball is a very infrequent occurrence on OS X, and if it does happen, it u
by TazeTSchnitzel 12y ago
> The beachball on OSX frequently causes the whole UI shell to freeze solid.
The beachball is a very infrequent occurrence on OS X, and if it does happen, it usually doesn't freeze the whole shell. If you're seeing it a lot, this is often an indicator of faulty hardware. That being said...
> This literally never happens on Windows.
Not true, the exact same thing can and does happen on Windows, with similar rarity.
> Also all IO on Windows is asynchronous. It doesn't support synchronous IO.
I'm not super-familiar with Windows IO, but at the very least it has blocking, synchronous C stdlib file I/O, and blocking, synchronous WinSock network I/O. Also, anything asynchronous can be trivially be made synchronous, whether it is a good idea or not.
- nbevans 12y agoSigh. You can't blame hardware when it's an as-new MBPr. Every Mac lover seems to blame it on something else when it is just a crappy OS that is the root cause. On Windows it is extremely rare - maybe once a year, but you'd have to be a power user for sure. On Mac, it is usually a weekly occurrence. Hell, I had it happen last night in fact just by trying to mount a DMG file (a freshly downloaded TeamViewer DMG if you must know). It decided to go to the beach instead. After a full reboot it finally let me mount it. It really is a joke of an OS. If you're not familiar with Windows IO then why try to cobble together a response? It is true that the Windows kernel does not support anything but asynchronous IO. It simply does not support it. Yes, user-mode land implements synchronous wrappers as a convenience for lazy developers or to aid in porting software from other lesser platforms.