Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hopefully a font fix for non retina displays. Not moving to Mojave until this is addressed.

Subpixel rendering isn't coming back. It never worked inside Core Animation, and the engineers will be happy to get rid of those special cases.

How about subpixel antialiasing for all of us non-retina users?

YOU CAN ENABLE SUBPIXEL ANTI-ALIASING if you want to.

But sure, keep on whining about it and ignore people telling you otherwise :rolleyes:
 
I can’t believe that apple so screwed up itunes audiobooks. It is crazy mess. Do they have different development teams then for music?? :-(
 
Worst release ever, Ugly UI, broken font readability, insane battery drains, even more choppy UI than HS, audio pops still present on the 2018 MBP’s, Safari hanging... what the hell Apple?
I strongly disagree with your assessment. On a 15" 2018 MBP, and I've been using since the betas. More stable than Sierra or High Sierra for me. UI looks great, battery life is strong, no audio pops, no Safari hanging, and no choppy UI elements.

Agree with others: don't project your experience on the Apple community at large.
 
Hopefully a font fix for non retina displays. Not moving to Mojave until this is addressed.

I used this command in Terminal and after logging out and back in it looks much better:

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO
 
Zero issues with that on my end. Again, sounds like you're experiencing a software or hardware glitch that needs to be looked at.

Unfortunately, Apple can't please everyone - but they can please most, as dark mode has almost universally been praised. You're actually the first person I've come across who doesn't like it.
I like a well done dark mode not this "dark mode" with a grey outline around windows and the dock, the greyish non translucent tones and the awful grey font on top of a dark grey texture which makes things unreadable.
 
I really am looking forward to Group FaceTime and hope it's in this version.

Also what is subpixel font rendering? does it make the font/text more sharp on non-retina displays?
 
I like a well done dark mode not this "dark mode" with a grey outline around windows and the dock, the greyish non translucent tones and the awful grey font on top of a dark grey texture which makes things unreadable.

That's totally fine if YOU don't like dark mode. But pretending like it's a bad UI that everyone dislikes is simply wrong.
[doublepost=1537908361][/doublepost]
So because you don't have problems, it means we can dismiss whoever does?

No, it means don't make blanket statements about issues when most are not having those issues. Certainly, report your issues (specifically to Apple, not just on a MacRumors forum), but realize not everyone is experiencing the same thing.
 
That's totally fine if YOU don't like dark mode. But pretending like it's a bad UI that everyone dislikes is simply wrong.
I simply stated my opinion, didn't say it's everyone elses opinion, did YOU read my first post or just follow the bandwagon?
 
YOU CAN ENABLE SUBPIXEL ANTI-ALIASING if you want to.

But sure, keep on whining about it and ignore people telling you otherwise :rolleyes:

You cannot. Before Mojave and starting with 10.5 Leopard which first shipped Core Animation, subpixel rendering was only available for non-layer-backed views (i.e. ones rendered without Core Animation, i.e. without GPU assist). For example, the translucent menu bar introduced in Leopard and made mandatory in 10.10 Yosemite never had subpixel-rendered text.

Starting in Mojave, most (all?) stuff gets opted into layer backing automatically. For layer-backed views, Apple never bothered to implement subpixel rendering.

As a result of those factors, subpixel rendering is basically a thing of the past.

I'm also not whining about everything. But no, you cannot enable it. There's nothing to "enable"; the implementation just isn't there (in Core Animation).
 
  • Like
Reactions: martyjmclean
I strongly disagree with your assessment. On a 15" 2018 MBP, and I've been using since the betas. More stable than Sierra or High Sierra for me. UI looks great, battery life is strong, no audio pops, no Safari hanging, and no choppy UI elements.

Agree with others: don't project your experience on the Apple community at large.
The only thing I'm going to "project" is this OS out of my Macs.
 
I used this command in Terminal and after logging out and back in it looks much better:

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

Does it work because I keep reading mixed messages that it doesn't really return the feature.
 
  • Like
Reactions: neliason
I simply stated my opinion, didn't say it's everyone elses opinion, did YOU read my first post or just follow the bandwagon?

Seriously, your first post:
"Worst release ever, Ugly UI, broken font readability, insane battery drains, even more choppy UI than HS, audio pops still present on the 2018 MBP’s, Safari hanging... what the hell Apple?"

Certainly comes across as a blanket statement and not your opinion.
 
You cannot. Before Mojave and starting with 10.5 Leopard which first shipped Core Animation, subpixel rendering was only available for non-layer-backed views (i.e. ones rendered without Core Animation, i.e. without GPU assist). For example, the translucent menu bar introduced in Leopard and made mandatory in 10.10 Yosemite never had subpixel-rendered text.

Starting in Mojave, most (all?) stuff gets opted into layer backing automatically. For layer-backed views, Apple never bothered to implement subpixel rendering.

As a result of those factors, subpixel rendering is basically a thing of the past.

I'm also not whining about everything. But no, you cannot enable it. There's nothing to "enable"; the implementation just isn't there (in Core Animation).

Well that sucks. Pretty stupid for Apple to do this when products still sold as new that will have crappy rendering fonts. Ridiculous.
 
Seriously, your first post:
"Worst release ever, Ugly UI, broken font readability, insane battery drains, even more choppy UI than HS, audio pops still present on the 2018 MBP’s, Safari hanging... what the hell Apple?"

Certainly comes across as a blanket statement and not your opinion.
Then you interpreted it wrong. From my experience with Mac OS X this is by far the worst one. Period. Even Yosemite was more stable, even Lion!
 
I simply stated my opinion, didn't say it's everyone elses opinion, did YOU read my first post or just follow the bandwagon?

Don't you think "Worst release ever, Ugly UI, broken font readability, insane battery drains, even more choppy UI than HS, audio pops still present on the 2018 MBP’s, Safari hanging... what the hell Apple?" is a bit of a stretch for "I simply stated my opinion"?
 
Don't you think "Worst release ever, Ugly UI, broken font readability, insane battery drains, even more choppy UI than HS, audio pops still present on the 2018 MBP’s, Safari hanging... what the hell Apple?" is a bit of a stretch for "I simply stated my opinion"?
If it was the case then I'd say the OS has been awful for everyone and that there have been a lot of user complains.
 
Then you interpreted it wrong. From my experience with Mac OS X this is by far the worst one. Period. Even Yosemite was more stable, even Lion!

There you go! Helps a lot when you add "from my experience" vs. just "worse release ever!"

It sucks that you're having a bad experience. Instead of complaining on these forums try reinstalling it to see if that helps. It certainly seems that most are not experiencing these issues - so there is something obviously glitchy on your end.
[doublepost=1537909153][/doublepost]
According to a poster on Reddit, it works like subpixel antialiasing: https://www.reddit.com/r/apple/comm...ve_nukes_subpixel_antialiasing_making/e6ggllr

I'm not sure how to revert this command, maybe someone who knows more about Terminal commands than I can help. Fortunately it makes the fonts on my Apple Cinema Display look decent again.

Reversing the cmd is as simple as changing the last NO to a YES
 
  • Like
Reactions: spullum
Does it work because I keep reading mixed messages that it doesn't really return the feature.

It works on my MBA and Apple Cinema Display, I'm not sure about other configurations.
[doublepost=1537909267][/doublepost]
There you go! Helps a lot when you add "from my experience" vs. just "worse release ever!"

It sucks that you're having a bad experience. Instead of complaining on these forums try reinstalling it to see if that helps. It certainly seems that most are not experiencing these issues - so there is something obviously glitchy on your end.
[doublepost=1537909153][/doublepost]

Reversing the cmd is as simple as changing the last NO to a YES

Thanks, I will keep that in mind, just in case.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.