I'd hardly say that... But the thing I've seen with High Sierra is that it's Apple's first attempt to start moving people over to the new APFS filesystem. Changing a whole file system is almost always a process that has some glitches or issues for a certain number of people.
On top of that? Apple really muddied the waters with the APFS rollout by not having it ready for use with Fusion drive configurations. (It just leaves those systems alone and doesn't attempt to convert them, which is fine -- but makes people feel like APFS isn't "ready for prime time yet".)
This AppleInsider article gives you some insight on why APFS is better:
http://appleinsider.com/articles/17...erra-apfs-benefits-end-users-with-space-speed
Among other things, they noted their test Mac booted up about 25% faster under APFS.
I've also noticed some more obscure changes with High Sierra over Sierra when using it in a corporate environment. For example? It used to be, if I connected to our office network by setting up a software "L2TP" VPN connection in Sierra? It worked fine, except I couldn't actually do the whole process of joining a new Mac to the Windows domain. It always threw error messages while attempting it. I had to make sure I was physically in our office, attached to the local network, if I wanted to do that initial one-time step of adding the Mac to the domain. In High Sierra, it worked for me - which tells me they improved some aspects of Windows networking and properly routing things over the VPN tunnel when one is set up.
Where I found High Sierra most frustrating is with the initial upgrade process from Sierra. Again, on our corporate Macs, we encountered some oddities -- including people's user profiles seeming to get mangled up on their machines, sometimes day or even a week after they moved to High Sierra. They could just create a whole new user account and put back their dock icons, software configuration settings, desktop background, and so forth -- and be back up and running.But something seemed to be getting damaged with migrating over their existing settings. Didn't always happen either. Only randomly.
On top of that? Apple really muddied the waters with the APFS rollout by not having it ready for use with Fusion drive configurations. (It just leaves those systems alone and doesn't attempt to convert them, which is fine -- but makes people feel like APFS isn't "ready for prime time yet".)
This AppleInsider article gives you some insight on why APFS is better:
http://appleinsider.com/articles/17...erra-apfs-benefits-end-users-with-space-speed
Among other things, they noted their test Mac booted up about 25% faster under APFS.
I've also noticed some more obscure changes with High Sierra over Sierra when using it in a corporate environment. For example? It used to be, if I connected to our office network by setting up a software "L2TP" VPN connection in Sierra? It worked fine, except I couldn't actually do the whole process of joining a new Mac to the Windows domain. It always threw error messages while attempting it. I had to make sure I was physically in our office, attached to the local network, if I wanted to do that initial one-time step of adding the Mac to the domain. In High Sierra, it worked for me - which tells me they improved some aspects of Windows networking and properly routing things over the VPN tunnel when one is set up.
Where I found High Sierra most frustrating is with the initial upgrade process from Sierra. Again, on our corporate Macs, we encountered some oddities -- including people's user profiles seeming to get mangled up on their machines, sometimes day or even a week after they moved to High Sierra. They could just create a whole new user account and put back their dock icons, software configuration settings, desktop background, and so forth -- and be back up and running.But something seemed to be getting damaged with migrating over their existing settings. Didn't always happen either. Only randomly.
