… impossible? for laptop that came with yosemite to be downgraded …
What's the model identifier of the Mac? You'll find it in System Information.
Firmware for Yosemite versus earlier versions of the operating system
… impossible? for laptop that came with yosemite to be downgraded …
I've been using Mountain Lion for a few weeks now. Here are my observations:
- Definitely boots faster than either Mavericks and Yosemite.
- Application response seems faster than Mavericks or Yosemite.
- BUGS - There are a few bugs with some of the applications, primarily Safari that don't exist in Mavericks.
The bugs aren't show stoppers, but they can be irritating. For example, sometimes Safari just crashes for no reason, sometimes when it isn't even doing anything. Another oddity is that the mouse pointer when using Safari can go to a spinning beach ball and stay there. The system isn't locked up, I can use Safari just fine, it's just that the cursor is the spinning beach ball as long as Safari is the active window. Another bug is that Notes once in a while can just up and delete a note, not only from the system but from my iPhone as weil.
I think Mavericks is a little more refined. More stuff seemed to work consistently, but like I said, none of the bugs in Mountain Lion are show stoppers. I've had no lock ups, no drive crashes, and really, no compatibility problems.
I would say for me the two best candidates that still offer services I want are still Mountain Lion and Mavericks.
I wonder if it's possible to create a Users folder that could be shared by all operating systems universally, meaning 10.6 through Yosemite. Anyone know if this is doable?
I'm a bit curious. In your adventures in OS X land, which browsers did you use. I seem to be finding that FireFox seems to be much more stable and up to date on older OS X versions that Safari. Chrome also seems fairly well kept up. I haven't tested any of these in detail, I just noticed that when accessing a news site on an older system recently that was running Snow Leopard, Safari was virtually useless, FireFox worked perfectly, and Chrome was OK but seemed to have a glitch here and there.
Yosemite tends to orphan some Web processes, and appears to spawn numerous copies while in use, often eating up tons of memory.
You're misunderstanding how modern browsers work. Each tab or window in Safari is now its own process. This is to improve reliability and security. If there's a crash in one tab or window, the browser will keep working and simply reload the crashed window. My computer has more than 2GB of RAM so I simply don't want all my apps to fit into 2GB and leave the other 14GB sitting around wasting my money.
That doesn't explain why their still around even after Safari's been closed.
That doesn't explain why their still around even after Safari's been closed.
I think what you are seeing is from having Spotlight suggestions turned on. I noticed the same thing. You search in Spotlight and it preloads some web search results there and those show in Activity Monitor looking like Safari instances when they are not.
So if I disable this feature then I assume some memory may free up, right?
FireFox seems to be much more stable and up to date on older OS X versions than Safari. Chrome also seems fairly well kept up. I haven't tested any of these in detail, I just noticed that when accessing a news site on an older system recently that was running Snow Leopard, Safari was virtually useless, FireFox worked perfectly, and Chrome was OK but seemed to have a glitch here and there.
Not sure Apple will be happy to hear I'm perfectly content running Snow Leopard .... but I get your point!
Ethanius said:Come WWDC this June I would like to see if Apple dared enough to post the OS X breakdown with Yosemite around less than 50% market share... Or will they rig the stats...
According to some recent sales reports they lost share in computer sales. Not by a lot, but they did lose a small section. WWDC is often filled with Rah-Rah boys and girls that will never complain about anything Apple does. What will be interesting to see is whether or not they even acknowledge there are any types of problems with what they're producing and its quality.
I booted off an external Snow Leopard partition and it booted almost as fast as Mountain Lion off an SSD. I ran Performance Probe on it and the memory use to run a Safari session with video was about 800MB total. I did the same experiment with Mountain Lion, Mavericks, and Yosemite.
As each OS gets newer, so does their RAM consumption. Yosemite's is somewhat higher than Mavericks, Mavericks is somewhat higher, but a little more noticeably than Mountain Lion. Both Lion and Snow Leopard use a pittance and both boot fast.
Has Apple just gotten into the bad coding habits process? Do they not bother to check the efficiency of what they produce anymore?
I booted off an external Snow Leopard partition and it booted almost as fast as Mountain Lion off an SSD. I ran Performance Probe on it and the memory use to run a Safari session with video was about 800MB total. I did the same experiment with Mountain Lion, Mavericks, and Yosemite.
As each OS gets newer, so does their RAM consumption. Yosemite's is somewhat higher than Mavericks, Mavericks is somewhat higher, but a little more noticeably than Mountain Lion. Both Lion and Snow Leopard use a pittance and both boot fast.
Has Apple just gotten into the bad coding habits process? Do they not bother to check the efficiency of what they produce anymore?
I'd say it's due to the constant new features that they introduced and the annual release cycles. Snow Leopard was efficient because their major new feature introduction was back in Leopard in 2007, and from this period up until 10.6.8, they had about 4 years of code cleaning and optimisation. That's 4 years...! Nowadays they emphasised on feature introductions before they could even clean up the bugs, what's more cleaning up the codes at 1/4 of the said period.
The more useless stuff OS X got, i.e. iCloud (sorry guys, I still believe in SyncServices), the more processes it needs to launch for every boots. Nevermind the RAM pressure zone Taz Mangus described, just fired up Activity Monitor on both SL and Yos and do a comparison, and you'll find more processes taking up your ever constant amount of RAM.
Now you see the successive buildup of craps post-SL. Every iteration of OS X since then has been more resource intensive. And just look at Finder alone. It got progressively worse off since Lion, now on Yosemite it is almost unusable.
I am convinced, beyond a reasonable doubt, that the reason Activity Monitor got rid of the memory pie chart and replaced it with "memory pressure" was to hide the fact that what they're producing is crude, poorly written, and memory excessive code. I remember during the early iterations of the extremely buggy releases of Mountain Lion, which remains buggy to this day, people were complaining about "memory pie charts gone-wild." They'd launch something with Safari and one minute it would say 100% of the memory was used and the next only a fraction of that was used.
Guys, memory use is reported by the kernel. If you want to check it using a command line program, you can do it with a program called vm_stat. This is the same stuff Activity Monitor used to monitor. Now it's hidden from us with "memory pressure." "Memory Pressure" in my opinion, is just a way of hiding poorly written code.
..and it shows in the newer OS releases performance. All those people leaving negative reviews about Yosemite's performance in the App Store aren't doing it for *****'s and grins.