Second, I hope we see better graphics, new OpenGL is a must.
Third, maybe a fresher UI similar to iTunes 11, would be nice. Aqua is dated.
That's all I hope for. Just wait for it, the announcement is tomorrow. It's only 21 hours away... just wait.
What is the business use case for a user to treat documents "Annual Report.docx" and "Annual report.docx" as absolutely different and unrelated?
To the average person, "John's grocery list" being different from "john's grocery list" would be nothing more than a silly limitation of the dumb computer.
How is a "case-sensitive" filesystem more ...modern?
Case-sensitivity has fewer edge cases (I'll give you that, especially concerning Unicode), but it's really just us bending over to the way the computer sees files instead of the way people think about them.
The files "accounts.xls" and "Accounts.xls" are not conceptually different.
>without resource or data forks of any kind.
Again, this is giving away tons of potential and actual benefits, features and uses, only to make it simpler for the developer of the filesystem and to enable better compatibility to cross-filesystems transfers.
I'd rather see a standard way of handling resource/data-forks that is also implemented by Windows and Linux at least.
It's more important considering Time Machine backups and actual UNIX moving and copying of files, and this is also where resource/data forks are also a huge burden. Unless OS X implements a different cp and mv than the standard FreeBSD ones, just implementing a filesystem without forking could be a solution. Also, case sensitivity is affected the same way.
For the normal user, it's fine to keep a case-preserving filesystem. But, Apple needs to make sure developers write their apps with case-sensitivity in mind (I'm looking at YOU, Adobe).
It does (though it didn't before 10.4). There's still lots of code out there that doesn't respect them, no doubt, but to my knowledge you can use the built-ins without worrying about losing your resource forks.
HFS has a case-sensitive flag. OS X works fine with it turned on. Some applications, notably games, sometimes have problems with it. You can easily create a case-sensitive development partition and have expect no problems.
Do people really play that many games on their Macs? And do they think 3.2 vs 4.x would make that much a difference?
And it's not like 2009 is that back. If you want to see real pain, see us web people not being able to use 5+ year old CSS technologies without tricks because of lack of support, and having to use an almost unchanged for 15+ years JS language.
Please do not justify brokenness by citing other brokenness.
It works on phones because phones have limited use cases. A computer needs to be general purpose.