Swift Is Now Open Source



Apple promised the people that it will make Swift open source by the end of this year and it came through. Swift is now open source and not only that, it’s compiler, libraries and debugger all are now open source as well.

The programming language has been released under Apple’s Apache 2.0 license which allows developers to use it any way they want to. They are free to use it in commercial products as well. The language also supports iOS, OS X and Linux.

A website has also been launched by Apple to introduce the language as an open source project. The website titled allows developers to access any sort of information to allow them to get started with Swift for any of their own projects including technical documentation and links to the source code which is also hosted by Apple on GitHub.

The website also states what Apple has planned for Swift 3. These plans reportedly include a number of things like API guidelines. Issues and comments regarding the language will be handled by the website and any contributions to the language should be made through the GitHub page.

According to GitHub’s head of open source Brandon Keepers “with the open source release of Swift on GitHub, Apple is bringing their modern programming language to the world’s largest development community. We warmly welcome Swift and can’t wait to see what the GitHub community builds with it.”

By making the language open source, Apple seems to encourage more and more developers to use Swift. As the core of the language can be integrated into any systems without any major issues it is expected that more and more developers will use this language. By allowing Swift to be open source Apple can improve its codes with the help of more programmers and it can no longer be accused of being a closed company.

Additionally the new IBM Swift Sandbox tool is also available for testing in beta form on developer Works website. The tool allows developers to write code and execute it in a server environment on top of Linux. The tool was detailed in a post made to IBM’s developer website by John Petitto.


Previous ArticleNext Article