This is very interesting, if not a little unexpected from my point of view. Overall it's very, very good thing, but I wonder whether this will present any problems for older applications expecting HFS+?
As some may know, OS X has had the option of using UFS filesystems since pretty much the beginning, and you could even use it for your boot partition. However, that simply didn't work with many "Mac" applications that expected certain HFS+ features to be there which were not (as opposed to "Unix" applications that only needed a basic filesystem which UFS more than adequately provides). Even though Apple included some workarounds to mimic resource forks and such on non-HFS+ filesystems, it simply wasn't enough, as many applications crashed or refused to run from a UFS partition.
Heck, even using case-sensitive HFS+ is not recommended for the system drive because some apps may assume case-insensitivity and expect the files "Readme" and "README" to be the same. It's bad programming on the app developer's part, but I'm sure it's not uncommon. Macs have been case-insensitive for what, 20 years or more?
ZFS does support forks, so presumably Apple will use this feature to continue to support resource forks and other extended file attributes for legacy apps that need them, but what about case insensitivity? I don't see anything mentioned in the Wikipedia page about the ability to run in a case insensitive mode. Will Apple add such a mode, or will they drop that feature, preventing many older apps from running properly?
Personally, I'm of the opinion that case insensitivity is a good thing, as filenames really only exist for humans to keep track of them. A computer can just as easily reference files by number and has no need for the names at all. So it makes sense that the names should ignore case since case rarely conveys any substantial meaning in human language.
What's Apple going to do here? Dropping case-insensitivity would be a step backwards IMO. It will be interesting to find out the details starting next week.