Some day I will learn that it’s nil in #Swift and null in #JSON but today is not that day

Is there a way to just straight-up force terminate a `.task` in SwiftUI? I'm not saying "ask it to please terminate when it's convenient 🥺", I mean "kill yourself right now and throw an error"

I'm running into a problem where I have some resource-intensive tasks that the user might want to kill, completely disregarding their current state. I tried looking it up, and every tutorial I've found is about the former variety. It might not be a best practice, but I swear I have a use case

We’re growing our product team!

Are you an #iOS Developer who wants to lead our official #Mastodon iOS #App?

This is a remote full-time position and requires an overlap with the CET timezone.

Ideally:

1. You are a senior iOS Developer comfortable with a mature codebase
2. Proficient in #Swift and #Apple Frameworks (UIKit, SwiftUI, Combine)
3. Prior experience with social media networks is a big plus!

For more info/to apply:
https://jobs.ashbyhq.com/mastodon/bc91c481-d30a-4e73-9eb8-ac29f4e905e2

I think the thing I find most frustrating about programming languages is that there is no standard way to refer to the length of an array.

Python, go: len(array)
Java, JavaScript: array.length
Rust: array.len()
C++: array.size()
C#: array.Length
PHP: count($array)
Perl: scalar(@array) (lmao)
Swift: array.count
Kotlin: array.size

Like, seriously? Can't we agree on just this one thing???

There's no official Swift Language account on Mastodon, is there? Still only on Twitter? :swift_app:

I was thinking that maybe I could try to talk someone there into starting to post on Mastodon and Bluesky too, given… <gestures around> you know

My beef about today's #Swift adoption at Apple is #SwiftUI. It is a framework that stands against what Swift promised to developers back in the days

- slow
- limited
- runtime crashes if you use the wrong variable type (compile and don't work?)
- unhelpful/misleading compilation diagnostics
- underlying objc frameworks crash and mem leak as it always been
- bad devtools that never improved