My opinion about Swift keeps deteriorating. Better than Objective-C, sure, but that's not a particularly high bar to beat.
I though the world has learned that exception handling is bad and that Java-style checked exceptions only make it worse.
When you accidentally forget to use flatMap and get Box<Box<Cat>>
Meet Umberto!
#CatsOfMastodon #swiftlang
When you accidentally forget to use flatMap and get Box<Box<Cat>>
Meet Umberto!
#CatsOfMastodon #swiftlang
#SwiftLang is such a nice scripting language. The only issue is that you basically always end up having to create a package.
Pro tip for when you do: use the `--type tool` flag
```
swift package init --type tool
```
when creating it. This will give you a nice scaffolding with ArgumentParser and the entry point already set up.
#SwiftLang is such a nice scripting language. The only issue is that you basically always end up having to create a package.
Pro tip for when you do: use the `--type tool` flag
```
swift package init --type tool
```
when creating it. This will give you a nice scaffolding with ArgumentParser and the entry point already set up.
Proxygen 4.0 is now available with client app lookup and helper tool that automatically configures system HTTP/HTTPS proxy for traffic monitoring.
Mac app available at https://proxygen.app and iPhone & iPad apps at App Store. Take it for a spin!
I wrote up a little flowchart here for how I think about "is it ok to do this work on the default Swift Concurrency thread pool?": https://forums.swift.org/t/is-concurrent-now-the-standard-tool-for-shifting-expensive-synchronous-work-off-the-main-actor/82976/17
When to make something asynchronous, when to make it parallel, and how parallel to make it are all inherently tricky in extremis, but the default behavior is the default for a reason, and is appropriate in the vast majority of cases.
I wrote up a little flowchart here for how I think about "is it ok to do this work on the default Swift Concurrency thread pool?": https://forums.swift.org/t/is-concurrent-now-the-standard-tool-for-shifting-expensive-synchronous-work-off-the-main-actor/82976/17
When to make something asynchronous, when to make it parallel, and how parallel to make it are all inherently tricky in extremis, but the default behavior is the default for a reason, and is appropriate in the vast majority of cases.
I'm thinking of getting a salaried job after years of freelancing. (The stress and overhead isn't worth it with a toddler, I'd rather have it calm.)
If you know someone who needs a #Swiftlang dev with 10+ years of experience, macOS and iOS, also some C and #Rust, who can self-manage and also manage-manage and act as product owner etc. (I'm also an indie with the full spectrum of experience), do share!
Thanks 🙏
(Remote from Bielefeld, Germany)
I'm thinking of getting a salaried job after years of freelancing. (The stress and overhead isn't worth it with a toddler, I'd rather have it calm.)
If you know someone who needs a #Swiftlang dev with 10+ years of experience, macOS and iOS, also some C and #Rust, who can self-manage and also manage-manage and act as product owner etc. (I'm also an indie with the full spectrum of experience), do share!
Thanks 🙏
(Remote from Bielefeld, Germany)
Community work in the Swift for Wasm ecosystem has gained momentum and deserves regular status updates at this point. Here's what we've achieved just in the last few months: https://forums.swift.org/t/swift-for-wasm-september-october-2025-updates/82966
Community work in the Swift for Wasm ecosystem has gained momentum and deserves regular status updates at this point. Here's what we've achieved just in the last few months: https://forums.swift.org/t/swift-for-wasm-september-october-2025-updates/82966
My opinion about Swift keeps deteriorating. Better than Objective-C, sure, but that's not a particularly high bar to beat.
I though the world has learned that exception handling is bad and that Java-style checked exceptions only make it worse.
Now in #SwiftLang review: The `@export` attribute, proposed by @dgregor79, is an expert library author’s utility knife. It does everything from replacing `@_alwaysEmitIntoClient` to helping Embedded Swift code encapsulate internal imports. Let us know what you think about it on the Swift Forums: https://forums.swift.org/t/se-0497-controlling-function-definition-visibility-in-clients/82666/1
Now in #SwiftLang review: The `@export` attribute, proposed by @dgregor79, is an expert library author’s utility knife. It does everything from replacing `@_alwaysEmitIntoClient` to helping Embedded Swift code encapsulate internal imports. Let us know what you think about it on the Swift Forums: https://forums.swift.org/t/se-0497-controlling-function-definition-visibility-in-clients/82666/1
