Originally Posted by myapplelove
Well, enumeration or not, if your machines run great, I m fine by that, anyway:
Buggy and problematic smb shares, slow, unreliable, no searching, problems with printers via smb.
safari memory leaks
Autoshutdown acing like program crash
Still no dpi or ri settings with ever shrinking font in higher and higher resolutions
annoying and/or buggy save states (close all safari windows, log out and in and they pop up again)
defualt versioning a problem
Frqeuent crashes in preview
mail going to 1-2gb memory
briken memory management with too many page outs, much larger kernel task memory allocation
poor performance in order macs where windows installations right now run much better and expand their life cycle
various ui problems in monochromatic user interface elements, iPad looking elements not well suited to macs, duplicate instead of save as etc., and in general it shows a tendency to pander to ios design but without good judgment on implementation , much like the new apple tv interface, the people overseeing ui choices are no Steve Jobs. It ales a lot of talent to go from decent o good to great and from convoluted to simple. Durrent os x ui design is very seldom well done. It's the difference between huddler and a good forum software.
poorly implemented mission control ui (about to be fixed in ml)
a generally slow system even on new macs, certainly not showcasing the state of the art hardware used
mcuh less responsive browsers both chrome and safari compared to windows (tried and tested in many devices) and flash now has be disabled by default in os x (yeah I don't like flash either, but it's a large part of the web still)
Poor legacy support, when g4 computers could run leopard, it's inexcusable that macs circa 2009 won't run mountain lion.
Its a poor release anyway you cut it, it brought many very unpolished and questionable "features", many bugs in major os software, and has had very ltle focus on core software development unlike sl. Apple isn't putting appropriate care to it, and they are too focused on its, their dev teams are enoguh, and the b team very obviously gets to work on os x.
Originally Posted by Dick Applebaum
Thanks for the detailed response -- I see some valid points there... And a few I will challenge.
Right now, I am watching the NBA playoffs -- so it will be later tonight.
First, are you Using Lion exclusively on Macs -- no Hackintoshes. I once believed that software is buggy and hardware is a rock-solid known entity -- hardware can be buggier than software.
Second, I believe with each release of OS X, Apple tries to establish a new threshold of minimum system requirements/capabilities while, at the same time, discarding whatever it can to minimize legacy bloat, This philosophy has served Apple and its users pretty well. Though, any particular OS X release may not suit specific users' needs -- my need for Rosetta requires me to run SNL on a single Mac. At any point in time, some of the OS features are not, yet, implemented in the OS -- they are being piloted in a few, select apps.
Third, I believe the iOsification of OS X is a good thing if done properly. Many legacy OS X constructs were reimplemented "the right way" for iOS, then ported back to the OS X mothership. Apple appears to be giving the Mac user the option to run the iOS UI along with the traditional OS X UI -- rather than cramming it down the users' throat, ala Metro.
Fourth, I believe that Apple knows where it wants to go with OS X, and basically this means that the OS becomes invisible (or at least gets out of the way) for most users -- while still satisfying the needs of the power user. Some day, in the not-too-distant future, Apple will celebrate the "arrival" by CTFF -- Can The Fine Finder.
Response to your specific points:
We don't use smb shares -- no comment
Safari memory leaks a periodic problem -- pretty responive fixes from Apple
Do not use autoshutdown -- Experience has shone better to keep things running (sleep)
I think DPI and RI will come in ML -- maybe with retina and GPU requirements
no problems here with saved states
versioning works fine for us
use Preview all the time -- can't remember any crashes
mail is 1.52 gb -- not a big deal here
mem management & kernel -- no information
poor performance on older Macs -- stay on older OS X version
monochromatic UI -- Apple trying things, SJ certainly approved Lion UI -- I think its a step in a series
mission control -- OK
slow -- see below
browsers and Flash -- seems as fast or faster than SNL
legacy support -- a plus and a minus -- you still can run an old OS X version
Finally let me demonstrate the future, as I see it:
I have used Final Cut for years... It is a powerful, but intricate, confusing and bloated piece of legacy [Carbon] software -- crash and error prone. It was updated every 12-18 months with mostly feature adds and bug fixes. Many users stay a release (or 2) behind.
FCP X was released less than a year ago -- completely rethought and reimplemented. It is wicked fast and fun to use. You never save anything (like iOS) it autosaves. You have fantastic metadata and search capability with an SQL DB (though you don't know it) file management system. You can do in minutes what it takes the older FCP hours to do, on the same hardware.
When first released, FCP X lacked some capabilities of the prior versions -- but it has been updated 4 times (fixes and features) in less than 12 months (obviously, some feature additions were already in development).
It cost 1/3 of the prior version.
FCP X is not for everybody... but it shows the future.
I believe that Apple does the same thing staging its OS releases:
-- establish a threshold
-- show some sizzle that exploits the threshold
-- discard legacy baggage
-- set the stage for the next release
So, any version of the OS is just a step along the road -- some better, some worse. In the case of OS X, you can stay on the current release or, for $30, download the latest version from the app store.
That's a pretty good accomplishment, IMO.
Paraphrasing: OS X is a journey, not a destination.
Edit: Just to follow up. The mail app on my system takes 1.75 MB RAM idle up to 1.52 GB when very busy. Compare that to the Flash plugin whick takes 1.75 GB RAM and 115% CPU when idle...
Edited by Dick Applebaum - 5/28/12 at 1:45pm