Swift at Apple: Migrating the TrueType hinting interpreter
1–10 of 139 posts
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#2During 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.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#3I 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
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#4During 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.
Curious the direction of Webkit as there was a nebulous mention of select portions being rewritten from C++ to Swift. And yet, the new ECMAScript module (ESM) loader for Safari 27 is implemented in C++ (https://webkit.org/blog/17967/news-from-wwdc26-webkit-in-saf...).
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#5I 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
I mean they’re doing both
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#6Interesting that this is published under the MIT, rather than Apple’s more favorite Apache 2, license
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#7The author discussed this a bit on Mastodon as well:
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#8Back 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.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#9Interesting that this is published under the MIT, rather than Apple’s more favorite Apache 2, license
Why is it interesting?
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#10I'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).