Here's hoping it fixes the issue I've been having since upgrading. My wifi doesn't drop, but my internet access stops working every 10 minutes or so. Cycling my wifi connected brings it back.
Really hope they fix the multiple display issues where menu bar icons are redrawn every time you switch displays causing flickering in your peripheral vision. Very annoying. According to the link below, this is "by design" but it clearly seems like a bug to me.
It is baffling to me how poorly apple, and their OS, has supported multiple monitors.
I heard anecdotes that it was passable on Mavericks, but prior to that there were all manner of basic usage problems.
It makes me think that there must be some kind of "apple way" resistance to multiple monitors ? Is it considered a "wrong" use-case ? Do people at apple not use multiple screens in their own work ? (how could they, with the issues that have plagued it since snow leopard...)
Mac OS and OS X always had good multi-monitor support. In 10.7+ Apple tried to push a "one app in fullscreen as in iOS" approach as new paradigm, negatively affecting the multi-monitor experience. It backfired and they adjusted in 10.9+.
This also baffles me. I have a number of friends who use OS X for development and some just use one large monitor + spaces but the majority use multiple monitors. None of them experienced this issue but we were unable to figure out (we didn't spend a lot of time on it) what was different about my setup from theirs. Maybe it just never manifested for Apple employees? That sounds a little ridiculous but I don't know what else to think.
I am not sure what you mean. Are you sure what you mean?
OSX (and I think even earlier MacOS) have supported multiple monitors for quite a long time, historically better than most other OSs. Many of us use multiple monitors on OSX with no problems. One neat thing OSX/MacOS have always done with multiple monitors is allow you drag windows from one to the other as if they were one big workspace -- even having a window partially on one monitor and partially on another, with it working fine.
What has happened recently is that the combination of the OSX UI, multiple monitors, and new features to support a 'full screen' mode (which seems to some people like a sort of convergence with iOS) -- have been problematic. Apple has had trouble deciding what _should_ happen with multiple monitors in this situation, and has had trouble making it work reliably.
Until the most recent OSX release, you could only do 'full screen' mode on your 'main' monitor, the other monitors would all go dark. Which was pretty annoying for those who wanted to use this newish feature. But other than that, multiple monitors had no real problems.
In the most recent OSX, they've tried to do some things to take care of this, so you can use 'full screen' mode on all your monitors (one 'full screen' workspace on each monitor). (Sadly, these things also get rid of the ability to have a window half on one monitor and half on another).
The solution they tried appears to have some technical problems. Which yes, is frustrating for people with multiple monitors, who want to use the 'full screen' feature, with the new improvements (which you can turn off if you want, to back to only being able to use one monitor in full screen mode).
I think many people do have a sense that Apple QA isn't quite as good as it used to be. And they do seem to be having trouble getting the new-ish 'full screen mode' (which people seem to like) to work reasonably with multiple monitors. But I don't think it accurately represents the history to suggest that OSX has historically poorly supported multiple monitors. I am not familiar with what you are referring to when you say "prior to [Mavericks] there were all manner of basic usage problems," that has not been my experience and I have not previously heard of such experience.
"even having a window partially on one monitor and partially on another, with it working fine."
Huh? In Safari, on 10.10 - dragging a window from my iMac to half on my TB display results in the window being partially visible on the iMac, and not at all visible on the TB. When you drag further to the TB display (so your mouse, but not the entire window is on the TB), then it snaps to the TB display. Both inconsistent and not at all what you describe. I don't have any windows so far I can get to sit across monitor boundaries.
Which I read later is related to 10.10?
So handling of multiple monitors is broken from one extreme (full screen pre Mavericks) to the other "Well, full screen works now, but your screens are effectively fenced off (Yosemite). Not sure how this is "better than most" support for multiple monitors.
"(which you can turn off if you want, to back to only being able to use one monitor in full screen mode)."
That's a horrible hack that with everyone's insistent claim on Apple's attention to detail and quality should never have made it passed QA.
Most Mac usage in the wild is in laptop form. It is really only the "geeks" who seem to be interested in using their laptops with external displays and setting up desktop-style workstations for them. Also, most Apple desktops are iMacs, which already have large, high-resolution displays.
The monitors built into Apple products are typically much better than consumer $150-$200 monitors and most externals look horrible side-by-side with Macs (dim, mismatched color, wildly lower pixel density, etc). It wasn't until I bought a $400 24" IPS UltraSharp that using an external monitor next to my laptop was actually preferable.
Transparency is definitely an eye candy-only thing that provides no benefit and comes with a performance hit too. This volume indicator wasn't fixed in 10.10.1 though http://i.imgur.com/Unh3EA1.png
I just updated all the way from Lion (10.8). It seems that every display has its own menu bar which I don't know if I like yet, but more disturbing to me is that one of my external monitors is flickering off for a second or two every minute or so after this upgrade. Not sure what the source of the issue is, but it was working fine before the upgrade. :/
I used to use a Matrox DualHead2Go DP Edition so I could use my two 19" monitors in addition to my main laptop screen. Earlier this year I bought a LandingZone docking bar which let me run one monitor via miniDV and the other via HDMI. This solution has worked pretty well so far, so I hope the flickering either magically fixes itself or that I'm able to find some cause and resolution. :)
I need my three monitors. I've never liked the whole idea of virtual desktops, etc. and I like being able to see mail, calendar, shell, and browser just by glancing instead of requiring any sort of gesture or keystroke.
This 10000x over!!! I posted in that thread [0] & [1] and ended up having to just disable "Displays have separate Spaces" because my clicks wouldn't register for 1-3 seconds when clicking into another monitor. Very annoyed by this issue and hope they fix it soon!
> You should back up your system before installation. To do this you can use Time Machine.
Except that Yosemite stopped recognizing my Time Machine drive because it was plugged in through a powered USB 3.0 hub.
It doesn't look like I'm the only one with this problem - if someone from Apple were to PM me, I could reply with the USB vendor & product ID to help get this solved.
Apple didn't drop support for 3rd-party SSDs, nor did they drop TRIM support, as it was never supported on 3rd-party SSDs. Rather, signature verification meant that an unofficial kext patch to make TRIM work on 3rd-party SSDs stopped working.
Low transparency mode has this weird bug where the corner of rounded rectangles are black rather than fully transparent. Try enabling it in accessibility and then changing the volume.
Edit: I wonder why I am being downvoted. UI/UX bugs are bugs as well and need to be addressed!
The UI does look terrible and, as the link I provided shows, many things people complain about are not a matter of personal taste, but actual reductions of usability.
I've been using it since 10.1, and the only time I thought they took a step back was with Mavericks. I attribute that to major UI changes needing a version to sort out.
I had this feeling of going back with Lion, when they removed the scroll bars.
It might look great, and I agree it's pretty slick and much more à la page if you will, but it's much less usable. Windows 8 looks so much better than 7 [1], but it's a train wreck in terms of discoverability and usability.
[1] one might argue that this flat UI trend originated at Microsoft that Apple is copying them and that some of the things Microsoft is doing now look much better than their Apple counterpart especially on mobile. I can't comment on usability, because I haven't tried either.
You are conflating UX with aesthetics. When you are saying that "the UI looks terrible even with transparancy dialed down" you are just saying the new Yosemite is ugly to look at.
That's a personal opinion and really doesn't matter on HN.
The link you provide is not about aesthetics, but about UX. So to back up your (pointless) claim that Yosemite is ugly to look at, you link to an article that rightly points out useability problems. This is like saying "The top speed of my car is too low, here's an article that talks about its slow acceleration"
I am assuming you are being downvoted because your claim is irrelevant to HN discussion and your link is irrelevant to your claim.
Your second claim is partially true though. While volume indicator does show black corners, there are plenty of rounded corners that do show correctly in Yosemite with transparency turned off.
Lastly, according to the HN guidelines, you are kindly asked to "Resist complaining about being downmodded. It never does any good, and it makes boring reading. "
Have they fixed cifs slowness in Yosemite? That would be my only reason for upgrading. I actually use a vm Windows for browsing network shares on my Mac it's so bad..
Perhaps you should switch up from cifs to smbfs? I used to use cifs in Maverick but now appear to get slightly better stability and performance using smbfs with my Window 2012 server and 10.10.
Is it just me or do the last iOS and OSX updates look really bad? I upgraded my iPhone to iOS 8 and somehow calls started dopping (even after 8.1 and resetting the entire device twice!). The Apple help desk actually asked me to install each app one-by-one to see if that finds a rogue app! Luckily, I was within a year of warranty and they replaced my iPhone.
I have not upgraded to OSX Yosemite yet. I am afraid that there will be a performance hit. Even the new iPhone 5S I got replaced faces some lags that weren't present in iOS 7.
What are your views about upgrading to Yosemite, esp. related to dev environments?
Edit: I have faced similar lags after updates on my iPad Air too. Hence, the dismay.
I've had a lot of wonkiness with Keychain, iCloud, and iMessage since the upgrades, but that seems to be because certain preferences were reset or deactivated in the process. (I'm also willing to accept user error as the culprit).
Have also had some weird issues with wifi connectivity, which is ostensibly one of the reasons for this update. And there have been some strange lockups on the mail screen on my iPad, occasionally forcing me to hard-close the mail app.
Other than that, I haven't noticed anything significantly "bad" about the updates. Yosemite has been fine for me, and aside from some third-party compatibility issues (which happen with every major OS upgrade), the upgrade has been seamless. iOS 8 performs well, aside from the aforementioned problems.
Whole system crashes have been much more common, especially ones related to sleep (the system won't wake up). About half a dozen to a dozen times since the upgrade (one month) but really, there shouldn't be any.
Out of curiosity did you fresh install or upgrade?
I'd upgraded since Leopard/Snow Leopard it had always just worked for me. Yosemite though had crashes and hanging - I decided a fresh install and it's been working great since.
Not the best news if you're used to upgrading but for me it worked wonders.
I did an upgrade and I'm considering wiping and doing a fresh install when I get some time. This is my primary work machine (it's a personal laptop but all my work stuff is on it) and so I'm hesitant to take any chances or do anything that could mess with my work timelines on projects.
I actually am in the same boat. Primary machine, both personal and projects on it. It is a lot of work to do a fresh install. It eats up a day and I do not have that. I was paying big bucks to Apple to solve this for me. Don't you think so?
"I was paying big bucks to Apple to solve this for me"
Agreed. I don't want to have to worry about shit like this. When I use Windows I would ALWAYS do a clean install and almost always do a clean install every few months because I run my machines hard (installing tons of stuff to try out then removing it). With OS X I didn't have to worry about this and have saved a TON of time not having to rebuild my computer with each release. I expect better from Apple.
I like (/don't care) about the new UI look in Yosemite but I have not been very impressed with it as a whole. The install took over 3 hours (I use homebrew and minor research I did pointed at that being the cause, well the cause being lots of data in /usr/local which is where HB puts it's stuff) and this [0] issue was causing me to pull my hair out until I just disabled per-display spaces to "fix" it. That menu bar issue would cause a 1-3 second delay between clicking on a monitor different from the one with the active window which was infuriating.
I was unaffected by the big issues (wifi) plaguing iOS 8 and didn't get burned by the 8.0.1 issue. I have the 6+ and I do have some weird issues still like BT Audio sometimes skipping a second or two when the screen rotates (I know... odd) or just screen rotation issues as a whole (I shouldn't have to shake my phone or switch orientations multiple times before it works!!). Also the healthkit stuff not working at release (because of a security bug) was annoying, where is the homekit integration?, handoff is gimmicky and I have found little/no use for it so far (I have a MBPr + iPhone + iPad, I expect better), keyboards where glitchy as fuck on release, Apple Pay didn't support either of my CC's and the process to setup a card was far from what I would expect from Apple.
All in all: Yes, both releases were shit if you ask me and that's coming from someone who loves Apple products and owns quite a few of them.
> All in all: Yes, both releases were shit if you ask me and that's coming from someone who loves Apple products and owns quite a few of them.
Thanks! I have similar thought and I have not even updated to Yosemite! Just the sheer amount of issues I read about online and my iOS disasters lead me to believe that Apple's entire update across the suite of products was not what it used to be. I left the Windows land to get the stable and tested products and updates. If I have to be locked down tremendously and face the issues I used to face with Windows, I might as well just use something where most of my development is - Linux.
Couldn't agree more. I love linux for servers and work with linux servers all day long but I don't like linux desktop or app selection as much. I think there is something to be said for using a beautiful interface and apps everyday and I haven't really seen anything in the linux world that come anywhere close (without HOURS AND HOURS of playing with configs). I bought into Apple for *nix environment that "just worked (tm)" if they push another bad OS X release then I'll have to seriously consider linux again...
OS X updates have been virtually flawless for me in the past. Yosemite is the first one with big problems:
- No longer able to connect to any 5GHz wifi routers.
- Wifi drops suddenly and won't reconnect automatically even though the network is present.
- Very slow wifi generally.
- Unable to restore from sleep, machine reboots.
- External display doesn't come up during login after sleep, need to open MacBook and login there.
- Random hangs/kernel panics. (Could be explained by faulty RAM, but starting to happen just after Yosemite upgrade? Doubt it.)
- Laggy UI.
The last point is the worst. "Reduce transparency" does nothing for me. WindowServer is occasionally using 20-30% when the system is doing almost no redrawing. Safari is sluggish, and often hangs for several seconds — especially on opening new blank tabs, loading a new site, trying to load an embedded YouTube video ("HTML5" mode) — before becoming responsive again. Overall, it feels like my machine (early 2013 MBP, quad-core 2.7GHz i7, 16GB, SSD) just rolled back two hardware generations.
Hopefully this update should fix the wifi issues. But the lagginess isn't mentioned in the release notes. Has anyone gotten any performance improvements by reinstalling the OS from scratch?
- Random hangs/kernel panics. (Could be explained by faulty RAM, but starting to happen just after Yosemite upgrade? Doubt it.)
Yup. Early 2013 15" rMBP, on Mavericks? Rock solid. Even on a fairly minimal clean install of Yosemite? Hard freezes, kernel panics.
iMac will occasionally come back from sleep with a all white screen except for my user logo. I can type (though can't see) my password and login, but the quality has gone horribly downhill.
- Random graphics glitches, especially in Safari. Random garbage/empty areas being painted.
- FileVault's encryption process doesn't finish. "Connect power adapter to resume encryption". It is connected. Has been doing this since I upgraded.
- If you enable "Reduced transparency", you get certain graphics artifacts. For example, the rounded corners on screen overlays such as the brightness and volume settings are painted in.
I see nothing about it, but I've noticed an issue with headphones (and maybe multiple monitors). If you plug in headphones while your laptop is asleep, then wake it up, it seems to crash with a "sleep wake failure". Once I found the issue I was able to help a lot of people stop their macs from crashing on wake as well. Really hope that one is fixed in this update.
My rMBP updated just fine to 10.10.1 but when I went to update my sister's MBP with a 840 SSD and Trim Enabled I ran into the grey forbidden screen and safe mode yielded the 'Waiting for root device' error. This can be fixed by going into recovery mode (Command+R) on boot and running the following commands:
Be aware this script (and Trim Enabler) require you to turn off kext signature validation. This feature was added in 10.9 but it only raised warnings on missing or invalid signatures. It didn't actually prevent the kext loading. 10.10 now raises an exception whenever you load an unsigned or invalidly signed kext.
Disabling this check returns you to 10.9-level security and removes barrier to malware installing its own kernel modules.
Yeah, unfortunately there is no way to enable TRIM without turning off signature validation completely. Apple calls the feature kext developer mode. It would be nice to see them providing more fine grained control over which kexts are supposed to run in dev mode — or just enable TRIM for non-Apple SSDs in the first place.
Ah, too bad there aren't any fixes listed for Bluetooth. I've been having all kinds of issues with device pairing and, once paired, connections dropping. I also suspect Bluetooth (or rather, searches for nonexistent BT input devices) to be the cause of very long delays when resuming from hibernation.
Disappointed that the update doesn't seem to mention graphics fixes. Many people (myself and my colleague included) are having issues with the dual gpu mbp retina. Graphics corruption, forced logouts, big black blocks - seems to happen while switching from intel to nvidia.
There doesn't appear to be any fixes for FileVault, which is rather disappointing. Under certain circumstances, particularly with new installs, FileVault can get into an inconsistent state and the only known cure (so far) is to erase the disk and reinstall.
Edit: Nope, FileVault is still broken after the patch.
No mention about fixes to the WindowServer using all available CPU either... When there's animation on the dock it happily uses ties up a core for as long as it can.
Sigh. It took Apple a month to release a relatively small and minor incremental update to an OS they launched over a month ago riddled with bugs and UI inconsistencies and issues.
This update is meant to address the wifi issues of intermittent connections, weak connections, constant dropouts and lost packets. Installing the update has not fixed the wifi issues and some Googling/Apple forums proves this. I have resorted to using my Dell laptop more than my Mac because the wifi issues have been too much to bear.
Apple used to be about quality. Mavericks was a fantastic operating system I had no such issues with. What are Apple doing over there? This is what happens when you put an industrial designer in charge of your software.
71 comments
[ 2.4 ms ] story [ 129 ms ] threadHere's hoping it fixes the issue I've been having since upgrading. My wifi doesn't drop, but my internet access stops working every 10 minutes or so. Cycling my wifi connected brings it back.
Open that in Script Editor and then export is as an application. Then just run that application whenever your wifi stops working for no reason.
http://apple.stackexchange.com/questions/152038/prevent-redr...
I heard anecdotes that it was passable on Mavericks, but prior to that there were all manner of basic usage problems.
It makes me think that there must be some kind of "apple way" resistance to multiple monitors ? Is it considered a "wrong" use-case ? Do people at apple not use multiple screens in their own work ? (how could they, with the issues that have plagued it since snow leopard...)
What's the deal ?
Mac OS and OS X always had good multi-monitor support. In 10.7+ Apple tried to push a "one app in fullscreen as in iOS" approach as new paradigm, negatively affecting the multi-monitor experience. It backfired and they adjusted in 10.9+.
OSX (and I think even earlier MacOS) have supported multiple monitors for quite a long time, historically better than most other OSs. Many of us use multiple monitors on OSX with no problems. One neat thing OSX/MacOS have always done with multiple monitors is allow you drag windows from one to the other as if they were one big workspace -- even having a window partially on one monitor and partially on another, with it working fine.
What has happened recently is that the combination of the OSX UI, multiple monitors, and new features to support a 'full screen' mode (which seems to some people like a sort of convergence with iOS) -- have been problematic. Apple has had trouble deciding what _should_ happen with multiple monitors in this situation, and has had trouble making it work reliably.
Until the most recent OSX release, you could only do 'full screen' mode on your 'main' monitor, the other monitors would all go dark. Which was pretty annoying for those who wanted to use this newish feature. But other than that, multiple monitors had no real problems.
In the most recent OSX, they've tried to do some things to take care of this, so you can use 'full screen' mode on all your monitors (one 'full screen' workspace on each monitor). (Sadly, these things also get rid of the ability to have a window half on one monitor and half on another).
The solution they tried appears to have some technical problems. Which yes, is frustrating for people with multiple monitors, who want to use the 'full screen' feature, with the new improvements (which you can turn off if you want, to back to only being able to use one monitor in full screen mode).
I think many people do have a sense that Apple QA isn't quite as good as it used to be. And they do seem to be having trouble getting the new-ish 'full screen mode' (which people seem to like) to work reasonably with multiple monitors. But I don't think it accurately represents the history to suggest that OSX has historically poorly supported multiple monitors. I am not familiar with what you are referring to when you say "prior to [Mavericks] there were all manner of basic usage problems," that has not been my experience and I have not previously heard of such experience.
Such as? And how?
"even having a window partially on one monitor and partially on another, with it working fine."
Huh? In Safari, on 10.10 - dragging a window from my iMac to half on my TB display results in the window being partially visible on the iMac, and not at all visible on the TB. When you drag further to the TB display (so your mouse, but not the entire window is on the TB), then it snaps to the TB display. Both inconsistent and not at all what you describe. I don't have any windows so far I can get to sit across monitor boundaries.
Which I read later is related to 10.10?
So handling of multiple monitors is broken from one extreme (full screen pre Mavericks) to the other "Well, full screen works now, but your screens are effectively fenced off (Yosemite). Not sure how this is "better than most" support for multiple monitors.
"(which you can turn off if you want, to back to only being able to use one monitor in full screen mode)."
That's a horrible hack that with everyone's insistent claim on Apple's attention to detail and quality should never have made it passed QA.
The monitors built into Apple products are typically much better than consumer $150-$200 monitors and most externals look horrible side-by-side with Macs (dim, mismatched color, wildly lower pixel density, etc). It wasn't until I bought a $400 24" IPS UltraSharp that using an external monitor next to my laptop was actually preferable.
I used to use a Matrox DualHead2Go DP Edition so I could use my two 19" monitors in addition to my main laptop screen. Earlier this year I bought a LandingZone docking bar which let me run one monitor via miniDV and the other via HDMI. This solution has worked pretty well so far, so I hope the flickering either magically fixes itself or that I'm able to find some cause and resolution. :)
I need my three monitors. I've never liked the whole idea of virtual desktops, etc. and I like being able to see mail, calendar, shell, and browser just by glancing instead of requiring any sort of gesture or keystroke.
[0] http://apple.stackexchange.com/questions/152038/prevent-redr...
[1] http://apple.stackexchange.com/questions/152038/prevent-redr...
Except that Yosemite stopped recognizing my Time Machine drive because it was plugged in through a powered USB 3.0 hub.
It doesn't look like I'm the only one with this problem - if someone from Apple were to PM me, I could reply with the USB vendor & product ID to help get this solved.
http://uxcritique.tumblr.com
Low transparency mode has this weird bug where the corner of rounded rectangles are black rather than fully transparent. Try enabling it in accessibility and then changing the volume.
Edit: I wonder why I am being downvoted. UI/UX bugs are bugs as well and need to be addressed!
I've been using it since 10.1, and the only time I thought they took a step back was with Mavericks. I attribute that to major UI changes needing a version to sort out.
It might look great, and I agree it's pretty slick and much more à la page if you will, but it's much less usable. Windows 8 looks so much better than 7 [1], but it's a train wreck in terms of discoverability and usability.
[1] one might argue that this flat UI trend originated at Microsoft that Apple is copying them and that some of the things Microsoft is doing now look much better than their Apple counterpart especially on mobile. I can't comment on usability, because I haven't tried either.
That's a personal opinion and really doesn't matter on HN.
The link you provide is not about aesthetics, but about UX. So to back up your (pointless) claim that Yosemite is ugly to look at, you link to an article that rightly points out useability problems. This is like saying "The top speed of my car is too low, here's an article that talks about its slow acceleration"
I am assuming you are being downvoted because your claim is irrelevant to HN discussion and your link is irrelevant to your claim.
Your second claim is partially true though. While volume indicator does show black corners, there are plenty of rounded corners that do show correctly in Yosemite with transparency turned off.
Lastly, according to the HN guidelines, you are kindly asked to "Resist complaining about being downmodded. It never does any good, and it makes boring reading. "
Jury is still out on 10.10.1.
I have not upgraded to OSX Yosemite yet. I am afraid that there will be a performance hit. Even the new iPhone 5S I got replaced faces some lags that weren't present in iOS 7.
What are your views about upgrading to Yosemite, esp. related to dev environments?
Edit: I have faced similar lags after updates on my iPad Air too. Hence, the dismay.
Have also had some weird issues with wifi connectivity, which is ostensibly one of the reasons for this update. And there have been some strange lockups on the mail screen on my iPad, occasionally forcing me to hard-close the mail app.
Other than that, I haven't noticed anything significantly "bad" about the updates. Yosemite has been fine for me, and aside from some third-party compatibility issues (which happen with every major OS upgrade), the upgrade has been seamless. iOS 8 performs well, aside from the aforementioned problems.
I'd upgraded since Leopard/Snow Leopard it had always just worked for me. Yosemite though had crashes and hanging - I decided a fresh install and it's been working great since.
Not the best news if you're used to upgrading but for me it worked wonders.
Agreed. I don't want to have to worry about shit like this. When I use Windows I would ALWAYS do a clean install and almost always do a clean install every few months because I run my machines hard (installing tons of stuff to try out then removing it). With OS X I didn't have to worry about this and have saved a TON of time not having to rebuild my computer with each release. I expect better from Apple.
I was unaffected by the big issues (wifi) plaguing iOS 8 and didn't get burned by the 8.0.1 issue. I have the 6+ and I do have some weird issues still like BT Audio sometimes skipping a second or two when the screen rotates (I know... odd) or just screen rotation issues as a whole (I shouldn't have to shake my phone or switch orientations multiple times before it works!!). Also the healthkit stuff not working at release (because of a security bug) was annoying, where is the homekit integration?, handoff is gimmicky and I have found little/no use for it so far (I have a MBPr + iPhone + iPad, I expect better), keyboards where glitchy as fuck on release, Apple Pay didn't support either of my CC's and the process to setup a card was far from what I would expect from Apple.
All in all: Yes, both releases were shit if you ask me and that's coming from someone who loves Apple products and owns quite a few of them.
[0] http://apple.stackexchange.com/questions/152038/prevent-redr...
Thanks! I have similar thought and I have not even updated to Yosemite! Just the sheer amount of issues I read about online and my iOS disasters lead me to believe that Apple's entire update across the suite of products was not what it used to be. I left the Windows land to get the stable and tested products and updates. If I have to be locked down tremendously and face the issues I used to face with Windows, I might as well just use something where most of my development is - Linux.
- No longer able to connect to any 5GHz wifi routers.
- Wifi drops suddenly and won't reconnect automatically even though the network is present.
- Very slow wifi generally.
- Unable to restore from sleep, machine reboots.
- External display doesn't come up during login after sleep, need to open MacBook and login there.
- Random hangs/kernel panics. (Could be explained by faulty RAM, but starting to happen just after Yosemite upgrade? Doubt it.)
- Laggy UI.
The last point is the worst. "Reduce transparency" does nothing for me. WindowServer is occasionally using 20-30% when the system is doing almost no redrawing. Safari is sluggish, and often hangs for several seconds — especially on opening new blank tabs, loading a new site, trying to load an embedded YouTube video ("HTML5" mode) — before becoming responsive again. Overall, it feels like my machine (early 2013 MBP, quad-core 2.7GHz i7, 16GB, SSD) just rolled back two hardware generations.
Hopefully this update should fix the wifi issues. But the lagginess isn't mentioned in the release notes. Has anyone gotten any performance improvements by reinstalling the OS from scratch?
Yup. Early 2013 15" rMBP, on Mavericks? Rock solid. Even on a fairly minimal clean install of Yosemite? Hard freezes, kernel panics.
iMac will occasionally come back from sleep with a all white screen except for my user logo. I can type (though can't see) my password and login, but the quality has gone horribly downhill.
- Random graphics glitches, especially in Safari. Random garbage/empty areas being painted.
- FileVault's encryption process doesn't finish. "Connect power adapter to resume encryption". It is connected. Has been doing this since I upgraded.
- If you enable "Reduced transparency", you get certain graphics artifacts. For example, the rounded corners on screen overlays such as the brightness and volume settings are painted in.
The news OSX Ysemite 10.10.1 Mail (v8.1) is a disaster. It keeps on crashing.
Commands Source: http://www.cindori.org/forums/topic/heads-up-osx-10-10-beta-...
Disabling this check returns you to 10.9-level security and removes barrier to malware installing its own kernel modules.
Edit: Nope, FileVault is still broken after the patch.
This update is meant to address the wifi issues of intermittent connections, weak connections, constant dropouts and lost packets. Installing the update has not fixed the wifi issues and some Googling/Apple forums proves this. I have resorted to using my Dell laptop more than my Mac because the wifi issues have been too much to bear.
Apple used to be about quality. Mavericks was a fantastic operating system I had no such issues with. What are Apple doing over there? This is what happens when you put an industrial designer in charge of your software.