Separate names with a comma.
Discussion in 'OS X El Capitan (10.11)' started by WizardHunt, Oct 2, 2015.
minor glitches here and there but as expected with every major release. Overall I'm happy I upgraded
Tend to agree, by the .1/.2 release the majority of software vendors/dev`s will have issued updates etc. am seeing them rolling in now. Going with the .0 release has always carried risk and will continue to do so for numerous reasons. For the sake of stability your always better off waiting a little.
A significant aspect is that peoples systems can and do vary significantly, the only way to guarantee a good OS update is to do your "homework" and ensure all your hardware & App`s are compliant with the new OS prior to pushing the "button" and the eternal "backup, backup, backup"
Why people proceed to update the OS without a solid backup solution is beyond me. Even if the computer is used solely recreationally dealing with a "borked" OS and or Apps without the basic skills rapidly escalates to being a "nightmare"
I don't use outlook so I cannot comment on that.
Of course after posting I had no problems with Word and Excel, both wouldn't close for me and I had to force quit them. There's not been a repeat of that behavior but I did want to pass that tidbit on.
I found El Capitan running slightly slower on my mid 2012 MBP with 8 gig of RAM. Random lag when swiping between Spaces which was a disappointment.
I'm not a fan of the new Mission Control. I find the top distracting with that shading and I wish I could disable it.
I'm getting the dreaded beachballs again. Not too many, but more often, and it concerns me. Beachballs had pretty well disappeared in Yosemite. In El Capitan, apps like MS Word 2011 bounced 14 times to open.
I find the San Francisco font to be smaller, thinner, and lighter which affects legibility even more so on my non-retina compared to Helvetica Neue in Yosemite. I had no legibility issues with Lucinda Grande. I would like to have the option to bold the system font.
I reverted back to Yosemite and there is no lag anymore. I know I could try a clean install, but what's the point right now. I will stay with Yosemite for a while because it already runs super fast on my MBP.
I'm so tired of fixing annoying bugs when updating to a major OS X.
Then perhaps not update before the first bugfix releases.
I have disabled SIP, so some of my 3rd party apps still work, but so far EL Cap feels like disaster is lurking just below the surface at every turn. Odd behavior creeps up all the time and I end up restarting a good deal of the time to fix little hangs. All in all, I wish I had stayed with Yosemite for a few more months. "unstable" would be the word I would use to describe 10.11. 10.11.1 so far, is as bad or worse.
maybe a single incident.
please see my thread
HELP - KeyChain lost issue???
is this something that will be fixed? I have a 2012 rMBP 15" that has this graphics card.. since upgrading to eL capitan I've found things choppy, scrolling choppy and even when the D GPU was engaged.
How do you feel feel about apple now?
So far I cannot get Juniper VPN Network Connect to work. It just hangs at "Establishing secure connection..."
I've tried the sudo nvram boot-args="kext-dev-mode=1" command prompt + reboot and no avail.
EDIT: Solved, had to disable "rootless"
I alway disconnect everything & stop any superfluous auto-starts before an OS update, makes sense to keep the installation as simple as possible. In general if a driver update is required it will be downloaded when you plug in the peripheral.
Yeah, I hope - so far to good.
I'm still reading this as you're thinking that Apple should have waited to release the update until Microsoft was ready with an Office 2011 patch. In a way they WERE, Office 2016 has been released. It's not Apple's fault that Microsoft hasn't yet patched a 4 year-old Office suite to work with an OS that has been out in full release for 5 days.
My install went quick, things seem to be working well on my MBP (Mini might get upgraded tonight).
I did find one bug - when using screen sharing, if I have a notification on the computer I'm using, the cursor does some weird things when interacting with the menu bar behind that notification
Bet I'm older than you And I certainly don't follow your advice. I have the luxury of having 7 internal storage devices on my cMP (5 are SSDs with OS's on them) So I can experiment. In a past life I was a Beta Tester for a number of software companies. I have always download Mac OS Betas. With El Capitan, since PB1, I have been using it on my SM951 as my main OS. This is the first time I did this with a Beta Mac OS. I luv it as I have explained in earlier posts. I do have a back SSD with the final release of El Cap installed and I do have 2 other SSDs with Yosemite and 1 SSD with Mavericks.
You are entitled to your opinion, but the shoe just doesn't fit everybody. I still have not updated my MBA to El Cap, since it is my travel machine, and I haven't gotten around to it yet. If you have only one machine and only one storage device than maybe your advice has merit, but for many of us on this forum, No Way!
I'm just not convinced that all these security changes to the OS are really necessary at all. I mean I don't ever recall having a security issue with Yosemite, or Mavericks, or ML or Lion or whatever. I feel like I'd rather take my chances with security and be able to run apps like Outlook and Word and even Logic without having to jump through hoops each year. Yes, I should have left Yos on my mac and gone back to work. It's 100% my fault.
Late 2013 rMBP with 4 gigs of RAM (!), updated for the second time (Mavericks->Yosemite->El Capitan) runs GREAT! A bit faster than Yosemite, animations are a bit smoother, no significant lag anywhere. My system is a mess of installed and uninstalled apps, Homebrew, several Java versions, with large RAW and PSD files from a DSLR scattered all around, so I'm quite happy that everything is working, fast and stable. (Except my Wacom tablet, but that's a matter of time). No regrets whatsoever.
I understand what you are saying. But why should a company announce and encourage the public to use a product that is in a "Beta" phase. All I heard from Apple was the new wonderful OS El Capitan! Not that it may not be compatible with existing hard drives, printers, scanners, etc. and that you should upgrade at your own risk. It appears that when a new operating system is released anymore, the "at your own risk" or more appropriately "at your own peril" should be a required disclaimer.
Sometimes clicking on a song in or opening Spotify seems to cause a kernel panic in the latest version of El Capitan.. which is really weird as there was never a problem in any of the betas. I don't know if Spotify is to blame, hardware, or OS X. Besides that, everything is running very well and much more smoothly than Yosemite.
People appear to be having more issues with El Capitan on their Macs than they do with Windows 10 on the same machines.
For me, except for the Finder not being good with very large image files and a Photoshop Open CL crash when attempting to resize images bigger (not fixed by latest NVidia driver update either), everything else has been fine so far.
For me it turned out to be a total disaster.
New Mac Pro, couple of weeks ago did a reinstall of Yosemite (clean install, not restored), decided to upgrade to El Capitan once it went live.
Everything went smooth and nice, reinstalled software, etc – but when resumed work things became horrible.
I run Fusion VM with Oracle Linux / DB while using OS X to develop a java application. Application itself is a content indexer, it performs quite a lot of network requests (HTTPClient) – and it seems that El Capitan has some major issues with that.
So major that it affects UI experience.
For some reason El Capitan starts stuttering on network requests after some time – opening new tab in Chrome or Safari takes several seconds, that sort of thing. Even as I type this I get random delays on keypresses. Reboot fixes this, but only for a hour or so.
This affects only network-related activity, for example java IDE (IDEA) works just fine.
Did everything in the book – reset PRAM, SMC, created new network location, disabled unused network interfaces. No luck.
Mavericks / Yosemite worked just fine with the same workload.
In Activity Monitor I can see 15-20% system load (which I think means there're some low-level problems going on), in Yosemite I saw this in "User" category, which is exactly how it's supposed to work.
Will probably downgrade to Yosemite, because this is starting to become ridiculous.
P.S. Ah yes, also having issues with B&W USB speakers – they stop working randomly, logs show AppleUSBAudio something freaking out.
Edit: 10.11.1 beta did not help in any way. Disabling SIP etc. did not help either. Sad panda.
I agree. Apple really pushes new releases to the public claiming it's a performance improvement. Then you find out that an important app no longer works or you get tons of beachballs and sluggishness. What about all the non-techies who don't have any clue on how to fix these bugs or don't feel comfortable restoring? Not fun at all and definitely costly.
I don't get that Apple releases 10.11.1 beta on September 21st. Why bother releasing El Capitan on September 30th. Why not wait?
Bottom line is someone sets a date, and like as not it`s commercially driven. Bringing OS X in line with IOS`s update frequency in my opinion has resulted in a poorer user experience with the desktop OS. The once legendary OS X stability has deteriorated for many, I just don't see the benefit of such a short cycle for a desktop OS, by the time the OS is stable for many it`s superseded with the new update being no issue for many, equally significant numbers do have problems.
There are only a couple of reasons why 10.11.1 beta was released so rapidly; either Apple is aware that 10.11.0 has some significant issues, or they are putting more focus on OS X in the "face" of Windows 10.
Since I installed El Capitan I feel that my battery drains faster. I have a 2008 aluminium MacBook. The rest is fine for me.
It's perfectly normal from development/management point of view. Release management is not "2+2=4".