How does High Sierra work for you?

[space-time]

I got some Macs running Mavericks, all with SSD. In a few weeks I plan to update the OS on these Macs to Low Sierra, I don't think I want to deal with the new file system at this time. Still, I was curious how is your experience with High Sierra?

EDIT: I didn't see the thread below, sorry.

[Tommie Milwaukee]

It killed the plug-ins that I had installed in GarageBand. Luckily, I had a clone so I was able to go back to Yosemite.

[modelamac]

space,

I'm having trouble deciding which OS I plan to stick with, Mac or El Cap. Probably El Cap. Sierra is a prep OS for High Sierra, IMHO. High Sierra is good, but does not offer that much over the older OSes FOR ME. None of the Mavericks color is back - same blah, hard-for-me-to-read GUI. I've adapted somewhat, but it takes longer to do stuff.

[space-time]

modelamac wrote:
... None of the Mavericks color is back - same blah, hard-for-me-to-read GUI. I've adapted somewhat, but it takes longer to do stuff.

isn't it sad that many of us have trouble with Apple GUI interfaces these days? we need to go into Accessibility and enable stuff that was originally designed for people with vision problems. I wonder how those folks manage.

[Zoidberg]

Once Adobe fixes the problems that Creative Cloud is having with it, I'll re-consider installation.

And why would they not be having problems? It's not as if Apple releases beta versions for half a year leading up to the release. No; why would a multi-million dollar corporation have at least a few people working with the upcoming system, when they can just say "Apple only just released High Sierra, and we're working with them to try to fix the problem", when a small team of a few people work diligently to make sure their "home-grown" software is ready to run as soon as the final is released.

I swear, as soon as Affinity releases an InDesign alternate, I'm gone. I'm really sick of Adobe and their nonsense.

[N-OS X-tasy!]

Zoidberg wrote:
I swear, as soon as Affinity releases an InDesign alternate, I'm gone. I'm really sick of Adobe and their nonsense.

Oh, the irony! It doesn't seem all that long ago when the hue and cry was "I swear, as soon as Adobe releases a QuarkXPress alternative, I'm gone. I'm really sick of Quark and their nonsense."

What's old is new again!

[Onamuji]

Zoidberg wrote:
Once Adobe fixes the problems that Creative Cloud is having with it, I'll re-consider installation.

And why would they not be having problems? It's not as if Apple releases beta versions for half a year leading up to the release.

At this point, the blame lies with Apple. They've hardly documented APFS at all. Lots of developers are killing themselves trying to implement fixes with only the barest idea of how stuff is working under the hood.

[decay]

I'm curious how a file-level application suite like Adobe CC would care if the drive is APFS or HFS+ ?

Does it read and write files to FAT32?

[Onamuji]

decay wrote:
I'm curious how a file-level application suite like Adobe CC would care if the drive is APFS or HFS+ ?

Does it read and write files to FAT32?

FAT's parameters are well known and well documented.

With this new file-system, literally, every read and write operation could be messed up. Every line of code that depends upon a record of a file name or location is a potential disaster waiting to happen.

Here's a developer thread that touches upon your line of inquiry, tho it's for iOS:
https://mjtsai.com/blog/2017/03/24/apfss...filenames/

[gabester]

Onamuji wrote:
[quote=Zoidberg]
Once Adobe fixes the problems... I'll re-consider installation.
...as if Apple releases beta versions for half a year leading up to the release.

They've hardly documented APFS at all.
Of course they haven't... Apple's of the opinion you should just trust their stuff to work, it's like magic, don't mess with or try to understand it. "Don't you understand how hard it is to write a new filesystem?" they'll ask, because they need to justify why they haven't done it in three decades. And besides, since it's one of those areas they don't want users or developers poking around in because we should just trust them that it works, why should they document it well for developers? What possible use could they have?