Skip to content(if available)orjump to list(if available)

Advent of Swift

Advent of Swift

5 comments

·December 14, 2025

ChefboyOG

I'm curious, in what niches are people using Swift for new applications these days? I've enjoyed working with Swift in the past (albeit in very limited capacities), but I haven't personally come across any Swift-based initiatives in a while. I had high hopes for Swift for TensorFlow, but it was ultimately killed off.

frizlab

Usually for native iOS/macOS applications.

I use it also for a server of mine (and generally any new project I have).

I have also a few open-source projects in Swift[1][2], but none known.

[1] https://github.com/xcode-actions

[2] https://github.com/Frizlab?tab=repositories&q=&type=&languag...

kris-s

>The string processing is powerful, but inconvenient when you want to do things like indexing by offsets or ranges, due to Unicode semantics. (This is probably a good thing in general.)

This is being too generous to Swift's poorly designed String API. The author gets into it immediately after the quote with an Array<Character> workaround, regex issues, and later Substring pain. It's not a fatal flaw, a language backed by one of the richest companies in the world can have few fatal flaws, but AoC in particular shines a light on it.

I really like Swift as an application/games language but I think it unlikely it can ever escape that domain.

frizlab

> poorly designed String API

I wholeheartedly disagree and counterpoint that all other String APIs are wrong (bold statement, I know). Accessing a random index of a String is a complex (slow) operation, and as such, should be reflected as complex in the code, especially since people usually think it is not complex.

If you want an array of UInt8, just use that.

The part about the regex I agree with. They are slow and that’s a shame. I do not personally use regex much though, and don’t think it should be done much in prod either, unless there are no other options.

Regarding the domain, I recognize it seems to have difficulties escaping the “native iOS/macOS apps,” but IMHO it should not. It is a language that is simple to use, with reasonable memory handling default (ARC), though it can also use the memory ownership model of rust. Generally speaking using Swift is possible everywhere. I use it personally for an app (native and web front, and back), and it is extremely cool.

Its ecosystem is also becoming quite interesting. Most of the libs are from Apple, yes, but they are also very qualitative.

All in all I think it’s shame Swift is not more used overall in the industry.

null

[deleted]