3 ms·
While I haven't switched to another OS, Yosemite has been the worst release of OS X that I've used (I've been an OS X user since Jaguar). The general rule is t
by jonhohle 12y ago
While I haven't switched to another OS, Yosemite has been the worst release of OS X that I've used (I've been an OS X user since Jaguar).
The general rule is to wait until at least 10.x.1 (or later), but even now, there are still bugs that indicate that there is little to no structure release or QA process at Apple, and it's likely that few teams have gotten the religion of testing.
* In 10.0.0, systems on Exchange in our office would
freeze after anywhere from 5-60 minutes. Only a hard
reboot would make them responsive.
* smart mailboxes no longer live update for me. I just
have to trut that the messages I've deleted or moved
will be gone when I manually reload the mailbox.
* replying to calendar events in Mail no longer provides
any indication that some action has been performed.
(Maybe this is related to the smart mailbox issue
above).
* Calendar will just stop drawing every once in a while
requiring a restart.
* Calendar frequently barfs on event updates and requires
reverting to the server version for any hope of
reconciling the changes.
* Safari frequently consumes all memory and all CPU for
lighter workloads than I used to run (because I know it
will go out of control at somepoint).
* The background of the login screen frequently has
graphical glitches which are likely caused by
overwriting areas of graphic or texture memory (this
seems to happen on Intel or dedicated graphics cards)
* iPhoto forced a database update, crashed in the middle
of the migration, and corrupted a decade old library.
This happened immediately after time machine told me
that it needed to start a new a backup and deleted my
most recent good backup.
With all of the pulled releases of iOS and Safari lately,I really hope someone at Apple is mandating some soul searching and release process changes. I'm not happy to act as Apple's QA department.
Edit: formatting
- yourad_io 12y agoSingle data point (me): The pains of switching were greatly exaggerated in my head. First you get a good base: Ubuntu / Debian / Fedora (?), etc. You may have to spend a few hours sorting out drivers. I personally haven't had to do so for ages. Then you ditch Unity (or $default) and try out a few window managers until you find what you like. Then you "fix it" by customising away your annoyances and tailor it to your workflow. I'm too tired to re-write this to sound less preachy - so downvotes are welcome - but I was a diehard OSX (up to 10.6) user until I put my toe in the Linux pool. I was expecting it to be freezing and "braced for impact", but actually, it was quite warm and inviting. Exception: If need OS X apps, your path may be met with more friction. If there's a Windows equivalent to the OS X app, give Wine a try (Windows Emulator) - I keep hearing about how it gives people grief, but as far as I've seen, even my (distinctly non-technical) mother has installed and used small Windows applications without a glitch (or even realising that she is running Windows applications on her Mint). I think I read about some Mac-wine kind of thing, but not sure how mature it is - Google will help you. To borrow a slogan: Just do it. You may be as surprised as I was.
- jonhohle 12y agoI migrated from desktop Linux to OS X and use FreeBSD and Linux on my other computers. OS X does more right (for me) than any other commercial or open source Unix or Unix-like system, but that doesn't mean its perfect, and its growing further from being perfect as time goes on.
- acdha 12y agoHave you tried this with a fresh account? I've only seen one of those problems (Mail being stealthy about Exchange calendar replies except for deleting the message). The fact that you're seeing graphical glitches sounds like you might have a hardware problem which could also explain the corrupted data.
- jonhohle 12y agoThere are numerous accounts of the graphical glitch issue. It only happens on the background layer, and its happening on a machine with integrated graphics, not one of the machines with well known AMD graphics issues. The type of artifact is very similar to texture memory being overwritten. It could very well be a hardware issue, but since it only happens at the login screen and it consistently happens only after the Yosemite update, I'm fairly certain its software.