7 ms·
Given that MacOS is primarily a personal OS, the slight decrease in performance, that I am sure will be fixed as it APFS matures, is completely unimportant. Wh
by noncoml 9y ago
Given that MacOS is primarily a personal OS, the slight decrease in performance, that I am sure will be fixed as it APFS matures, is completely unimportant.
What is important however is that file name are finally case sensitive! (I know you could do the same with HFS+, but some applications didn’t support it, ie Adobe)
- microcolonel 9y agoFilesystem performance is one of the main bottlenecks for OS X applications (including consumer applications).
- noncoml 9y agoI never had any problems, but maybe I am not using the same applications. Can you give some examples? I guess video editing might be one, but I cannot think of many more.
- kobeya 9y agoLarge Photo or iTunes libraries? Video editing?
- microcolonel 9y agoCommon applications like the Finder and the Dock query the filesystem when you open a context menu, among many other things that don't intuitively seem to be filesystem-dependent. But then there are applications which have a reasonable excuse to be hitting the filesystem, like iTunes or Photos or Mail. They absolutely redline the filesystem on a regular basis. The basic speed of the flash storage in a MacBook Pro frequently masks these problems, but the filesystem works against it.
- RJIb8RBYxzAMX9u 9y agoPerhaps my use case is a bit esoteric, but lack of sparse file support in HFS+ is mildly annoying. Sometimes I would forget and accidentally create a huge one, then I'd have to wait for the OS to finish zero-padding (it's non-interruptible) or fail with ENOSPC. Having a fast SSD helps. :-)
- burnte 9y agoI've never liked case-sensitivity in file-systems, personally. I've always found it to be annoying with no utility that I could discern. If main.h and Main.h are truly different, I find it more useful to make the file name more descriptive than just changing letters. Would you tell me why you find it useful? Not an argument, I'd like to know what other people do with that feature.
- noncoml 9y agoPersonally I don’t care, but got interoperability problems a couple of times. One has to be very careful when they share a git repository between case-sensitive and case-insensitive OSes
- notamy 9y ago> Would you tell me why you find it useful? I think you answered this yourself: > If main.h and Main.h are truly different, I find it more useful to make the file name more descriptive than just changing letters. I truly doubt that most users - especially non-technical users - actually would do this.
- burnte 9y agoThen what utility does it have?
- 0x0 9y agoI was of the impression that APFS would still default to case insensitive. And if it does change the default to case sensitive, wouldn't it still break apps like Adobe and Steam etc? I mean, if their problem is that they refer to internal files with the incorrect case, what does it matter how the FS is implemented on a low level.
- noncoml 9y ago> I was of the impression that APFS would still default to case insensitive. I am of the impression that you are right. I got it wrong.