It's a joke compared to the ruby on rails or node ecosystem. It is about ecosystems, not languages. Swift's ecosystem is Apple products. If you're not doing t

It's a joke compared to the ruby on rails or node ecosystem. It is about ecosystems, not languages. Swift's ecosystem is Apple products. If you're not doing that, don't use Swift. You will have to learn and use multiple languages and multiple ecosystems regardless because each ecosystem insists on using its own language and tools. So just use the most popular one for each - it will be the most polished with the fewest number of gotchas. At this point, the clear winners for each ecosystem are Kotlin, Swift, Typescript, C# and C++ if you're doing games. If you write a todo app on each platform, you'll realize you're using the same set of language features with different syntax - that should lessen the anxiety of learning a new language. Once you're free and nimble, you'd have to be nuts to choose anything but the right tool for the job or when in doubt, the most popular.