logoalt Hacker News

Swift at Apple: Migrating the TrueType hinting interpreter

120 pointsby DASDyesterday at 7:54 PM51 commentsview on HN

Comments

pjmlpyesterday at 8:48 PM

During the State of Platform keynote, on the subject of Swift adoption across macOS, several examples were given, not only TrueType engine.

RIS is happening across all OS levels, if the keynote is to be believed.

show 3 replies
saagarjhayesterday at 9:04 PM

Interesting that this is published under the MIT, rather than Apple’s more favorite Apache 2, license

show 1 reply
mrpippyyesterday at 9:06 PM

The author discussed this a bit on Mastodon as well:

https://xoxo.zone/@numist/116716469017975106

show 1 reply
weinzierlyesterday at 9:15 PM

Back in 2023 there was talks about Microsoft rewriting the font stuff in Rust for similar reasons Apple is now doing the Swift move.

I'm not sure what became of it and if it ever shipped. If anyone knows I'd be curious.

show 1 reply
airstrikeyesterday at 9:30 PM

As much as I enjoyed Swift, one can only wonder what the world would look like if they had gone with Rust as their default language instead.

show 3 replies
AndriyKunitsynyesterday at 10:51 PM

What's funny is from 2023 (I think), macOS just draws the UI unhinted. You have a 1080p display and you don't want to see the letters in the UI blurred to death? Tough luck, 1080p is incompatible with macOS, everybody needs "retina", and nobody cares that Windows and all Linux DEs look on 1080p just fine.

It looks like this hinter will be used only in rendering PDFs, because that's where they test the performance.

show 3 replies
raphlinusyesterday at 10:12 PM

Welcome to the club of doing high performance text in a memory safe language!

LoganDarkyesterday at 9:21 PM

I'm surprised the code has visible LLM smells. Though, I shouldn't be surprised. I hope the important bits are still human-controlled (and the same for Apple's many operating systems that absolutely deserve to remain stable and understood).

show 2 replies
troupoyesterday at 8:58 PM

I think these are the types of things Apple should've focused on instead of half-heartedly barging ahead with SwiftUI and breaking the language in the process

show 1 reply
wg0yesterday at 10:14 PM

No mention of AI? Hand written code?

show 1 reply