Skip to Content/article-new/2014/06/swift.png?lossy)
Apple today announced Swift 2, the latest version of its programming language for iOS, OS X and watchOS with all-new Whole Module Optimization technology. Apple executive Craig Federighi also announced that Swift will be open source and made available for Linux later this year.
Swift 2 has new features that will enable developers to write even better code, including advanced error handling, availability checking and syntax enhancements.
Apple Fitness+ and Peloton offer polished workout routines delivered by enthusiastic instructors and accompanied by motivating music playlists.
Apple is rumored to be working on a new version of the AirPods Pro, the AirPods Pro 2, and there could be some design changes in store.
Apple is working on a Tile-like Bluetooth tracking device that's designed to be attached to items like keys and wallets for tracking purposes, letting you find them right in the Find My app.
Apple Augmented Reality Glasses are said to be coming in the next couple of years. Here's what we know so far.
Top Rated Comments
The news would be big if Apple was trying to create a cross platform language and tool set, like what Microsoft is doing. But they are not. While someone might adopt Swift for their own platform development (like Linux) you are not going to get Google or Microsoft using Swift, well maybe Google, but I am still sure at some level Apple would forbid that from happening.
There is a lot of misinformation in this post...If Apple wanted wider adoption then they should have made Swift for Visual Studio on Windows. There is like 1000 to 1 more people developing on Visual Studio, including ALL the enterprise and professional development that is on that platform. But then Microsoft has already taken care of that with Visual Studio 2015 and Xamarin support to build native iOS apps right in Visual Studio.
In fact Microsoft will do more for Apple then Apple is doing for themselves by opening up Swift. Having millions of developers with access to native iOS development on Visual Studio 2015, including a new Visual Studio client for OS X, is already way more exposure then Swift has gained to date. I can easily see far more professional and enterprise apps being developed on Visual Studio, targeting all platforms, then Swift still being used largely to cater to proprietary development for iOS and OS X.
But, even among my friends that develop on OS X, iOS, they don't use Swift themselves, say its nice but years away from being great.
The big news was Microsoft offering native iOS developent on Windows with Visual Studio 2015. This will do more to open up iOS development to a wider core of developers then Swift will ever be capable of.
First off, Swift is open source now. That's not just a phrase, that comes with a set of rules meaning no, Apple can't prevent Google from using Swift if its open source.
Being open source means if Microsoft wants to adopt it in to Visual Studio they can, this isn't something Apple can do, they do not own Visual Studio and can't force Microsoft to adopt their stuff in the same way Microsoft can't up and develop .Net for Xcode.
Apple's finally tailoring Swift
I see what you did thereYes, he was fired for using Swift. MacRumors does not site their sources inside Apple. That affirms that I have no obligation to site mine.
I call ********, how do you get fired for using a new language unless that WASN'T what you were supposed to do? His superior said to him "I know you've been using SWIFT like we told you to...so you're fired"? Come on..
Why Swift 2 and it's open source?
what are you talking about? can you post links to sustain your claim that Swift usage is very low? and that you know a guy who was "fried" from his job because, Swift?Notice how they did not mention adoption rate of Swift. Those I trust have told me it's adoption level has been very low. I know one guy fried from his job using Swift due to the instability of the language leading to release dates.
They tried the high road academic PARC types to come up with a next generation language and they fell short. The elimination of header files created way too much combining overhead than anticipated. Also the amount of pushback for even inside Apple was more than anticipated.