| Github | https://github.com/mackoj |
| Sambot | https://www.sambot.app |
| https://twitter.com/jeffreymacko |
Got a response to the DTS support ticket I opened about TextKit 2 performance. Apple confirmed the bug, told me there is no workaround, and refunded the ticket. Honestly, this is incredibly useful information with a turn-around time of ~ 3 days. That's now three TSIs in a row that have been useful, in at least some way.
Use those technical support incidents!
Wow! Thx @jegnux! And you know, you inspire me too! 😊
Really happy to be here in this great community with this awesome @ivory app, it’s like a fresh start!
So if you want to fill your timeline with great content: Follow these awesome French iOS/macOS developers working on indie apps 🚀
Have a great day folks! 😊
@jegnux
@frboulais
@Alexisbar @deanatoire @Cykelero @scalbatty @performat @mackoj @nverinaud @vtourraine @dimillian
I can’t be the only one who thought about it so…
#FollowFriday of French iOS developers working on indie apps. They all inspire me. @Alexisbar @deanatoire @Cykelero @scalbatty @julienlacr0ix @performat @mackoj @nverinaud @vtourraine @frboulais and of course, @dimillian
The recent announcement of the new Swift Foundation library didn’t share the most exciting pieces.
David Smith explains: https://cohost.org/Catfish-Man/post/557578-i-sup-with-a-lot-of
I with a lot of help from a few awesome teammates completed the careful Tetris game I've been playing with chunks of iOS/macOS since 2018! Before: Swift -> Foundation -> CoreFoundation -> ICU After: Foundation -> Swift (Foundation and CF still link ICU, but Swift no longer has any dependencies above libsystem/libobjc) This means that now * Foundation has the option to use a memory safe language internally * Most system components that Foundation depends on have the option to use a memory safe language internally * Embedded environments like the Secure Enclave can use Swift * Pure-Swift processes use less memory * Swift Strings use less memory and are faster * Swift WebAssembly programs can be much smaller to download * NSString<->String bridging can use Foundation/CoreFoundation internals directly, resulting in some speedups * The barrier to entry for adopting Swift in system components is lower, since they're already linking the runtime There's much more to be done, but multi-year projects coming together feels real good. On a more personal note, I've made a ton of progress in recovering from some traumatic events in 2020, and kinda feel like I'm back to being me.
I'm very pleased to announce that the Swift Language Workgroup has accepted "Using Swift from C++", a vision for how Swift APIs can be imported into C++! Congratulations to Alex Lorenz and the rest of the C++ interoperability workgroup!
https://forums.swift.org/t/accepted-a-vision-for-using-swift-from-c/62102
Hello, Swift community. I'm pleased to announced that the Language Workgroup has accepted its first vision document, entitled Using Swift from C++: This vision document presents a high level overview of the "reverse" (i.e. Swift-to-C++) half of the C++ interoperability Swift language feature. It highlights the key principles and goals that determine how Swift APIs are exposed to C++ users. It also outlines the evolution process for this feature. This document does not present the final design...
Ok, so everyone seems pretty into passkeys (WebAuthn). Here's the start of the experiment trying out Passkeys with Swift and serverless AWS. #ServerSideSwift
Steve Troughton-Smith
Matt Massicotte
Julien
Alexandre.swift ⚡️
jegnux
Miguel de Icaza ᯅ🍉
John McCall
Javi
