I think this signals that a huge group of computers are about eliminated from 10.12 update this summer. I think it also means a bigger change than normal with the software this year as well. The last time they went this long with supplemental updates was 10.6 and when Lion came out we saw a major departure from from they typical OS X look and feature set. Since 10.8-10.11 has been supported on macs that are now almost 10 years old now I'd expect that nothing older than 2010-2011 will be supported on the new update. They are trying to make 10.11 as stable as possible for the millions that will be left behind. Guess it's time for me to invest in a new Mac...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds First OS X 10.11.6 El Capitan Beta to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
As a Mac user, it's a relief to see someone, who really has the experience to provide tech support for both Macs and Windows, to say this. Nevertheless, as a Mac lover who is still on Mavericks, it hurts to see that El Capitan, which was meant to be a refinement of its predecessor and comparable to snow leopard, is only getting 2.5-star rating for the current version in the app store.
LOL! So we both downgraded our OS... For different reasons in this case, but nontheless!
I dont understand why Apple does not allow users to choose UI design to some extent. Leopard for example had a switch for "old" dock style that i immediately used until they removed the switch.
I went to Mountain Lion. How is the system performance under Mavericks?
There is a lot to fix, I hear you! My MBP for instance won't go to sleep anymore. It only hibernates and sucks my battery empty like I was running a max-battery-drain benchmark while the lid is closed. Its becoming ridiculous to be honest. I was actually buying a Mac to get rid of these very issues..
Last edited:
At this point, there are two kinds of new feature upgrades - those isolated to a single OS (such as modifications to Full Screen mode), and cross-ecosystem changes. It seems that most new features released during interim updates are cross-ecosystem features, like password protected Notes (supported on iCloud, OS X and iOS), while OS/platform-specific changes seem to be reserved for major releases.
I'm sure it will be to certain people on MR.
But it was destined to be so regardless of what was in it.
I beg to differ.
At this point I'm not even sure anymore whether they aren't even "least terrible" anymore, because Google is really catching up.
(whilst Microsoft, as always, tries to stay true to their roots and making awful interface decisions left and right. Granted, Windows 10 reverted a bunch of really awful decisions though not enough to make me say it's caught up to Windows 7, which remains the most consistently designed modern Windows to date.)
Glassed Silver:mac
Well, given the number of bugs, which for sure exist but which I still don't see too critical, increased life cycles and development periods might result in better quality.
It seems there are just too many OS to be accomplished every year...
Last edited:
This probably means that there are some significant security changes landing in the Fuji beta next month, and Apple needs a vehicle ready to go to deliver those same fixes to 10.11 users the same day. Otherwise there is a patch gap where fixed exploits are discoverable, if not documented, in 10.12 but unfixed in 10.11.
A non-experimental version of Metal, for example (one that at least tries to have feature parity with other APIs and also exposes the capabilities of the hardware more fully). An improved file system — Apple has laid some very impressive groundwork with CoreStorage, but its still in very early stages.
In software, Apple puts innovation above all. This is why they are constantly releasing unfinished, pre-release software products. I have witnessed how this works on the example of Swift, after it has been open-sourced. This is both the advantage and a disadvantage of Apple platforms, but its a feature by design. I would certainly not recommend a Mac for long-term software stability. To make it clear: I don't see it as a negative thing. In fact, I think Apple's way of 'just wrap up what we have, release it, look how it works, change the bits that don't' is a great way and without it Apple wound't be where it is now. But it should be clear that stability always (slightly) suffers with such a strategy. Apple is doing really good job keeping things consistent (they even go so far as to replicate known bugs from certain OS X releases so that software linked against those releases still work), but its a tricky balance, given on how extremely complex the OS is.
Huh. Just a couple days ago I had my 2011 iMac on 10.11.5 wake up to a black screen and beach ball. Had to hard reboot. Glad they are still working bugs out.
Sure a lot of bugs/fixes to iron out with all these betas / updates. Im glad they are proactive though. I hope the iTunes bug cannot connect to store issue is fixed as noted here https://forums.macrumors.com/thread...t-complete-your-itunes-store-request.1949665/
Would like to put in a vote for Mavericks being the last good OS X release. (I'd personally prefer 10.8’s UI with 10.9’s everything else, but that's just me.) I know I have no intentions of updating. Hell, I'm still using iOS 6.
I'm also looking for a build that completely breaks my computer, so that Time Machine backup won't be in vain.
OS X 10.12 alpha?
If true, then we should certainly see a 10.11.7 and even 10.11.8 before 10.12 comes out. I, like a few others, would welcome that refinement for this particular OS. Still have some weird lagginess at times with both my MacBook pro's that run 10.11.5, so the longer they can tighten up the El Capitan ship, the better IMO.
A 10.11.6 update. That was unexpected.
For some reason this has me worried Apple will drop some older Mac models in 10.12.
For some reason this has me worried Apple will drop some older Mac models in 10.12.
I had this issue once, when a connection persisted from an other computer via SMB. I changed file-sharing back to AFP and the problem went away...
So you saw a pattern (no .6 releases for a while) and decided it represented a rule. Verrrry logical
