2008 ... the first Mac I boughtWhich year is your Core 2 Duo?
2008 ... the first Mac I boughtWhich year is your Core 2 Duo?
Mail was extremely unstable for me on yosemite. Wifi and external monitor support were also very wonky. Really annoying and affected my productivity. El capitan, fixed those for me. I miss the old days when upgrading OS X was mostly pain free (used OS X since Tiger, and I felt Yosemite was the worst so far).I am actually of the opinion that people who said that bought into Apple's "stable as a rock" promo. 10.10.5 seems much less buggy than 10.11.2 to me.
2008 ... the first Mac I bought
Was that 10.10.5 though? I am only talking about the final release. It fixed my wifi problems for instance. I've not used Mail before 10.11, the 10.11.0 beta version caused my provider to cut me off as it wouldn't login correctly and they thought I was a hacker but since then it's been working OK.Mail was extremely unstable for me on yosemite. Wifi and external monitor support were also very wonky. Really annoying and affected my productivity. El capitan, fixed those for me. I miss the old days when upgrading OS X was mostly pain free (used OS X since Tiger, and I felt Yosemite was the worst so far).
So if my math is correct running El Capitan on this machine is more or less like running 10.6 on a Powerbook G4. No wonder it feels slow compared to SL... While El Capitan on my Mac Pro 1,1 is running extremely well (with the help of a SSD), on my 2009 mini it's not very pleasant, I'm considering reverting back to Mavericks on this machine as OS X gets too demanding for it.
Incorrect; I'm running El Crap on an iMac I bought last summer.
*********[doublepost=1452706256][/doublepost]I still have not upgraded to EL Capitan, as I still don't trust it. Has anyone put it off to install until say just recently? What was the reason you did not want to install earlier? Incompatible with some software? If So which software? Did you find a solution or did upgrading to EL Captian fix things?
I have installed-upon--and ran--multiple installations of ElCap on a local, traditional 7200RPM HD (e.g., rotational, platter-based, spinning fixed-disk hard-drive) these past few months to test whether I would be met with differences which left me wanting for more, or failing to meet my basic expectations:
What works for me?
How much change am I able to tolerate?
Where do I want to go?
My needs are few, and my software-requirements are minimal, yet I have always been game to roll with the changes.
I've been running 10.11.2 (15C50) for over a week, now, with my first install in which I used the Migration Assistant to pull my System Experience from my current Yosemite installation, and I was--frankly--taken-aback by the seamlessness of the process.
I was waiting a bit for ElCap updates for some software updates, but, well, all that's obligatory these days....
That for which I waited was basically time to personally test how this foux-'upgrade' would function.
I'm rollin' with the original 2006 Mac Pro (ordered November 11, 2006, and delivered, well . . . the snow was thick, and stuff <smile>), and I have the advantage of being able to have four fixed-disks installed at any one time.
I've been running OSX on Solid-State Drives (OWC for the first, then Toshiba Q-Series Pros for the remainder) for three years, and have grown accustomed to how responsive my System performs.
Testing ElCap installs on a 7200rpm spinner has been, well, humbling, to say the least . . . the time I've spent waiting, and waiting, and . . . running these installs was entirely more fluid, but not nearly as prompt as my latest installs on SSD's.
I did not need to do these things, but I wanted to, and the road to where I am has been most gratifying.
Short story-long...
I have no immediate regrets, and am currently--happily--where I was ten years ago:
Editing photos, building websites, creating art, email'ing my Dad, syncing Notes from my phone to my desktop in real-time, watching kittei videos on teh Toobs, participating in code-(de)construction with cool-as-**** people in other countries (hi, @Pike R. Alpha! hi, @PeterHolbrook!), filing my taxes (gak!), installing WIFI/BT wafers manufactured for a 2015 iMac the size of a postage-stamp I bought-of eBay from some guy in China into a piece of hardware manufactured in 2006 . . . it's all, completely fsck'n awesome.
I'll not be looking-back for one, single second
Nevertheless, you really do need to test it yerself . . . only then, will you be able to Know.
Regards, splifingate
It's almost like Apple didn't test el crapitan on anything older than c.2 years+ old hardware..
Works fine when it's pre installed ( imac 5k ) , not so good on my older macs ...
Total disaster on a 2011 mini
El Capitan is fine on anything with an SSD - Its not so good on any older hardware with 5400RPM drives - though its not too great on Apple's current hardware (Non Retina Macbook Pro, iMac and Mac Mini with 5400RPM drives).
It's almost like Apple didn't test el crapitan on anything older than c.2 years+ old hardware..
Works fine when it's pre installed ( imac 5k ) , not so good on my older macs ...
Total disaster on a 2011 mini
I'm really getting tired of the bugs I encounter daily. The latest one? I can't install 3rd-party Safari extensions. Clicking the "Trust" button that pops up in Safari doesn't do anything. Apple's software quality is just a shambles right now.
I run El Capitan on a 2008 aluminum MacBook and all is fine.
I have a bunch of extensions since the initial release of El Capitan and all work as expected.
I want to add that I haven't done a clean install since my transition of PowerPC to Intel based Macs. I don't know what you guys have done to your systems to cause problems but even my 8 year old MacBooks runs El Capitan quite well.
Ok I'll check it out. Thanks.not really, but check the file /var/log/system.log for 'wake reason'
Found it from the log. Looks like one of my Apple TV 2, which is currently sleeping, send attempt connection to the iMac every 10-15 min. Should I reboot that ATV 2 or do a Restore?not really, but check the file /var/log/system.log for 'wake reason'