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).
Swift at Apple: Migrating the TrueType hinting interpreter
11–20 of 139 posts
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#12Re: Swift at Apple: Migrating the TrueType hinting interpreter
#13During 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... ).
In any case I would have liked to have more info during the deep dive sessions.
As it is, Meet with Apple on security (a 5h long event) had much more information.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#14I'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).
From what I got Apple is using claude code A LOT internally
It worries me. I hope Codex adoption picks up there.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#15Re: Swift at Apple: Migrating the TrueType hinting interpreter
#16I'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).
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#17As 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.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#18Back 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
#19The author discussed this a bit on Mastodon as well: https://xoxo.zone/@numist/116716469017975106
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#20As 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.
Modern Swift borrows a lot from Rust! And it also has its own benefits, both ergonomic and also supporting eg generic in dynamic libraries
The gap between the two languages is quite small, it just makes me wish Apple was also all-in on Rust