Hacker News new | past | comments | ask | show | jobs | submit login

I would not consider a brand new file system to not be notable. Maybe for average consumers it wouldn't matter much, but for us, we probably should appreciate how big an endeavour a new file system is.



I certainly appreciated it when I went to install the beta this afternoon. Took two seconds to add a volume, as opposed to many minutes (and the risk of data loss) partitioning in the old days.


In my case it resulted in total data loss causing me to do a fresh install, then within days a file system that was filled to capacity due to time machine snapshots that couldn't be deleted due to a cyclical depedency. I had to figure out how to reinstall on HFS+ and don't plan on ever trying again.


It's a "brand new" file system with implementation details that are a disaster. Lots of apps - including Steam just don't work on it if you use case sensitivity. Which is just silly. I had to create a virtual disk and mount it in my install folder so steam could work. It's 2018.. my 3k macbookpro shouldn't have this problem.

Give me my damn physical escape key back! the touchbar is the silliest thing ever.


While I have many issues with the new file systems as well, it is difficult to justify blaming it for Steam not running. Steam for Mac had never ran with case sensitive file systems since its inception, and Valve continuously refused to fix this despite numerous user complaints. This is hardly Appleā€™s fault.


I was saying this almost 10 years ago with various applications blowing up on case sensitive HFSX, and not really getting very good reasons why. And it's not just a few developers, they were all telling me case sensitivity on macOS is a problem. They'd get things working with one build, and a new dev build would bust their app but only on a case sensitive file system, not case insensitive. So the fact it's 2018 and this is still going on with APFS? shrug It doesn't surprise me one bit, even though I don't understand why it's still a problem. Two different file systems, same problem. Sounds like Apple just doesn't really care to properly support or test case sensitivity, their own test suite doesn't catch problems in the real world?


As much as I value the new file system (interestingly architected by the chap who did the BeFS, if only Apple had bought Be Inc!), it appears to still be lacking all the wonderful features of NTFS.

I'm still on Sierra at the moment as I delay upgrading after all the horrible bugs of the new release have been found - in everyone's opinion, is now a good time to leapfrog High Sierra? Time will tell.


Anecdote is not data, but I had huge issues when I first updated, so I rolled back. About 6 weeks ago I bit the bullet and updated again and it's been fine.


Thank you - anecdotes help me because I know 1 other Mac user and he's not overly technical (day job is Windows C++ so there's little Apple love around here)


It was notable when it nuked my install drive on update and I had to restore from backup ;) That was a first for me with an Apple OS.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: