7 comments

  • pjmlp 1 hour ago
    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.

    • DASD 1 hour ago
      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...).
      • pjmlp 43 minutes ago
        No idea, maybe the private parts of the code, Safari isn't open source, or is coming later.

        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.

  • airstrike 39 minutes ago
    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.
    • jadengeller 25 minutes ago
      Modern Swift borrows a lot from Rust! And it also has its own benefits, both ergonomic and also supporting eg generic in dynamic libraries
      • ecshafer 6 minutes ago
        Swift and Rust were developed at similar times. I think of them more as having similar influences than borrowing from each other.
        • est31 1 minute ago
          Similar times and the Rust originator went on to work on Swift after it.
      • airstrike 16 minutes ago
        These days I mainly write Rust but I did write a semi complex iOS app and enjoyed Swift. I just didn't love how slow the type checker was and how it got lost. I recall having to break things into smaller bits to help the compiler, and there were some oddities about the language.

        The gap between the two languages is quite small, it just makes me wish Apple was also all-in on Rust

      • vardump 15 minutes ago
        Does it borrow borrow checker?
  • weinzierl 54 minutes ago
    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.

  • saagarjha 1 hour ago
    Interesting that this is published under the MIT, rather than Apple’s more favorite Apache 2, license
    • JumpCrisscross 48 minutes ago
      Why is it interesting?
      • drob518 44 minutes ago
        Presumably because MIT is even more permissive and it’s a change in Apple’s behavior.
  • mrpippy 1 hour ago
    The author discussed this a bit on Mastodon as well:

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

    • numist 24 minutes ago
      I'm also here :)
  • LoganDark 48 minutes ago
    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).
    • airspeedswift 37 minutes ago
      I assure you, every inch of the interpreter code has been stared at by humans, a lot. TBH even the assembly generated by it has.
    • dgellow 47 minutes ago
      From what I got Apple is using claude code A LOT internally
      • Cassell 9 minutes ago
        It would be interesting to see their internal guidance on LLM use. It’s a massive amount of new power that has to be wielded carefully. That kind of guidance might mean the survival or downfall of some big corps in the next few years.
      • wahnfrieden 39 minutes ago
        Yes they are using Claude Code - not the Xcode agents.

        It worries me. I hope Codex adoption picks up there.

  • troupo 1 hour ago
    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
    • saagarjha 1 hour ago
      I mean they’re doing both