[thih9]

> why would I waste my time working on a language that is too tied to the Apple platform

This might work the other way round: starting from people familiar with macos or ios development who want to write for other platforms.

Then the question becomes: why would a developer learn a different open source language when they can use what they already know. And sure, depending on the context they might still go with Python/Kotlin/Rust/etc.

[hu3]

> people familiar with macos or ios development who want to write for other platforms.

This is a rather small userbase when it comes to enterprise.

Especially because Swift will never be as versatile as Python or as efficient as Rust.

And then there's also Go, C# and Kotlin with much better tooling.

[privacyis1mp]

Xcode gives me such a hard time that I started considering writing in Kotlin for macOS, just to have a normal IDE. We used to have AppCode (from JetBrains) and it was great. I wonder why Apple didn't support JetBrains, after all, it would have been to Apple's benefit.

[ChrisMarshallNY]

Personally, I never liked AppCode. It was too much like Eclipse (which I also never liked).

Me not liking something, does not make it bad. It’s just not my choice. I’m glad it existed, because it probably prompted Apple to do better with Xcode. Lots of people that I respect, used it.

These days, Xcode is Big Bug Ranch. When “Delete the DerivedData folder” is S. O. P. for developers, and Apple tweaked Xcode to reduce its impact on the project, you know that they have waved a white flag to bugs.

[joseda-hg]

There's even history of it working before, with Google / Kotlin

[pjmlp]

Since Apple has moved themselves out of the server market, folks need to at least be able to target BSD/Linux server workloads, and naturally using Swift as well instead of another language is a desired option.

[makeitdouble]

That crowd has the disadvantage of not being primarily interested in the other platforms, so they won't be much invested in optimizing or better matching the target capabilities.

That's the same dynamic as web devs writing React Native apps: you won't expect them to contribute extensions that manipulate local apfs metadata for instance.

So while it's nice to have them use the tools, you still need people who primarily care for non Apple platform and embrance swift for their purpose to have it expand.

[qaq]

Hmm Snowflake and Apple are rewriting FoundationDB in Swift. Swift has pretty good dev. ergonomics and good interop with C/C++ so it might find it's niche outside of Apple.

[pjmlp]

That crowd needs other platforms when using servers, as Apple has moved itself out of the server market, so at very least BSD/Linux workloads.