2025 - the year when all developers the world over, all of them at once, were absolutely right.
October 30, 2025 at 1:42 PM
2025 - the year when all developers the world over, all of them at once, were absolutely right.
2025 summer vibes be like:
August 25, 2025 at 8:53 AM
2025 summer vibes be like:
I don't share that disappointment. I like typed throws. You don't need `do` ceremony if your block can fail with that type of error. A simple example is below. In a real app the error could have many cases, allowing you to compose the process as you need.
June 25, 2025 at 11:23 AM
I don't share that disappointment. I like typed throws. You don't need `do` ceremony if your block can fail with that type of error. A simple example is below. In a real app the error could have many cases, allowing you to compose the process as you need.
That's quite unfair given this year's update to iPadOS. I'm actually thinking they went too far. 4 windows on an 11-inch screen? We will squint our eyes out.
June 11, 2025 at 8:06 AM
That's quite unfair given this year's update to iPadOS. I'm actually thinking they went too far. 4 windows on an 11-inch screen? We will squint our eyes out.
Word of the day: **monomorphization**.
It jumped at me during my ongoing deep dive into dispatch mechanisms of @swift.org.
So anyway, here is a monomorph, the compiled younger brother of the xenomorph.
Have a fun #WWDC everybody! 🥳
It jumped at me during my ongoing deep dive into dispatch mechanisms of @swift.org.
So anyway, here is a monomorph, the compiled younger brother of the xenomorph.
Have a fun #WWDC everybody! 🥳
June 9, 2025 at 1:59 PM
Word of the day: **monomorphization**.
It jumped at me during my ongoing deep dive into dispatch mechanisms of @swift.org.
So anyway, here is a monomorph, the compiled younger brother of the xenomorph.
Have a fun #WWDC everybody! 🥳
It jumped at me during my ongoing deep dive into dispatch mechanisms of @swift.org.
So anyway, here is a monomorph, the compiled younger brother of the xenomorph.
Have a fun #WWDC everybody! 🥳
It also allows you to crash SwiftUI in record time if you aren't careful 😀
May 26, 2025 at 2:44 PM
It also allows you to crash SwiftUI in record time if you aren't careful 😀
I suppose in that case we could use the async let syntax. But it feels like we would be using extra decorations at definition as well as caller for something that currently does not need those decorations.
March 5, 2025 at 1:20 PM
I suppose in that case we could use the async let syntax. But it feels like we would be using extra decorations at definition as well as caller for something that currently does not need those decorations.
Hmm. If isolation inheritance was expanded from sync to async functions explicitly marked with `nonisolated`, wouldn't that break our ability to easily build structured concurrency? For example see here.
March 5, 2025 at 1:13 PM
Hmm. If isolation inheritance was expanded from sync to async functions explicitly marked with `nonisolated`, wouldn't that break our ability to easily build structured concurrency? For example see here.
A more accurate name for this keyword would have been `ignoreIsolationDefinition`. Because what this keyword really allows us to do is break the rule that isolation is controlled by definitions.
March 5, 2025 at 9:48 AM
A more accurate name for this keyword would have been `ignoreIsolationDefinition`. Because what this keyword really allows us to do is break the rule that isolation is controlled by definitions.
Second, *synchronous* functions marked non-isolated will still be isolated to the actor context of the caller, because isolation is never changed between synchronous calls. Although it may not be the actor of the context where the function was defined.
March 5, 2025 at 9:48 AM
Second, *synchronous* functions marked non-isolated will still be isolated to the actor context of the caller, because isolation is never changed between synchronous calls. Although it may not be the actor of the context where the function was defined.
First, functions can be non-isolated even without this keyword. For example, if defined in a non-isolated context.
March 5, 2025 at 9:48 AM
First, functions can be non-isolated even without this keyword. For example, if defined in a non-isolated context.
Shoutout to @bring-shrubbery.bsky.social, who created the absolutely amazing SVG to #SwiftUI Shape converter. 🔥 Made my day!
February 26, 2025 at 7:18 AM
Shoutout to @bring-shrubbery.bsky.social, who created the absolutely amazing SVG to #SwiftUI Shape converter. 🔥 Made my day!
This should not be needed.
February 8, 2025 at 6:54 PM
This should not be needed.
ha, day 4 here of staring at RealityKit. My life was really nice before quaternions 😭
January 13, 2025 at 8:21 PM
ha, day 4 here of staring at RealityKit. My life was really nice before quaternions 😭
Here's what I have in mind. Obviously the design leaves a lot to be desired, but hopefully it gets the idea across. If you tap a different emoji, the blue rectangle shifts to that emoji instead. IMO it would be clearer than a 2-line flow layout.
January 8, 2025 at 7:33 PM
Here's what I have in mind. Obviously the design leaves a lot to be desired, but hopefully it gets the idea across. If you tap a different emoji, the blue rectangle shifts to that emoji instead. IMO it would be clearer than a 2-line flow layout.
Siri after it sets screen brightness to 100% just before you go to bed:
"iS thIs bRigHt enOuGh foR yOu??"
"iS thIs bRigHt enOuGh foR yOu??"
January 3, 2025 at 9:12 AM
Siri after it sets screen brightness to 100% just before you go to bed:
"iS thIs bRigHt enOuGh foR yOu??"
"iS thIs bRigHt enOuGh foR yOu??"
🎄🍪Christmas gingerbread: ✅
December 9, 2024 at 6:38 PM
🎄🍪Christmas gingerbread: ✅