←back to thread

612 points dayanruben | 1 comments | | HN request time: 0.001s | source
Show context
uhura ◴[] No.42901158[source]
I believe that this long game of Swift being "good for everything" but "better for Apple platforms" will be detrimental to the language. This does not help the language nor seems to bring more people to the ecosystem.

Competitors seems to have a combination of: - Being more open-source - Have more contributors - Have a narrower scope

Maybe they should consider open sourcing all the tooling (like Xcode) otherwise the gap will only grow over time when compared to other languages.

replies(10): >>42901489 #>>42901515 #>>42901558 #>>42902281 #>>42902484 #>>42903459 #>>42903586 #>>42903797 #>>42905687 #>>42906498 #
JTyQZSnP3cQGa8B ◴[] No.42901558[source]
This has been my experience for a long time. Swift is nice but why would I waste my time working on a language that is too tied to the Apple platform even if it's open-source when we have more universal scripting languages like Python, or languages like Kotlin that are compiled but have more support (because I trust JetBrains way more than Apple at the moment), or languages that are most strict like Rust but have more momentum and safety?

They painted themselves in a corner. Apple being the best computing platform while trying to please everyone can never be a serious proposition. Either they are the best and everyone uses macOS, or we have to be so careful that any alternative is more interesting that what they propose.

replies(7): >>42901756 #>>42901778 #>>42902195 #>>42902203 #>>42902864 #>>42905718 #>>42907045 #
thih9 ◴[] No.42901756[source]
> 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.

replies(2): >>42903096 #>>42903873 #
makeitdouble ◴[] No.42903873{3}[source]
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.

replies(2): >>42904311 #>>42906657 #
1. qaq ◴[] No.42904311{4}[source]
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.