If you go back in time 15 years, and ask yourself if it would have been a good idea to be an "Objective-C" developer, I think the answer would have been "not re

If you go back in time 15 years, and ask yourself if it would have been a good idea to be an "Objective-C" developer, I think the answer would have been "not really, unless you only want to develop for MacOS". Swift is in pretty much the same situation, but for MacOS and iOS. There's no right or wrong answer here. Personally, I wouldn't define myself solely by using a single language. After working on projects using various domain-specific languages like 4GL and others, I would certainly bear in mind the risks that such a commitment would entail. While other commenters have mentioned the large iOS market share and the size of Apple, I would also caution that neither guarantee the longevity of the language or the relevance of your skills if they ever decide to pivot to something new. And there's plenty of historical precedent for that--I'd argue that it's a matter of when, and not if, it will eventually be replaced. Swift might eventually see wider adoption on other platforms. However, people are rightly cautious of vendor-specific and/or vendor-controlled languages, and I suspect its traction, like that of Objective-C, will remain low.