Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

Apple moves to open-source, unify Swift component across platforms

Apple has made the build system in its high-level programming language Swift — used by llbuild, the Swift Package Manager and Swift Playground — officially open source.

Apple formally contributed the code of Swift Build to GitHub on February 1. The repository contributed by Apple also includes support for Windows and Linux, alongside Apple's platforms.

Build systems take the code the programmer writes and turn that work into standard components like libraries and command-line tools used to create working applications. Currently, Swift offers two different build managers, which the Swift team identified as a source of developer issues.

Apple now wants to make the new Swift Build component the only build system, which will work across all supported platforms. Swift Build is part of the Swift Package Manager — a key component of Xcode, Apple's integrated development environment for macOS.

Towards a more open Swift language

In a related development, Swift has adopted the code of conduct defined by the Contributor Covenant, a code of conduct for contributors to free/open source software projects. The Swift team noted that the covenent "is used across many open source communities, and we think it articulates our values well."

According to Apple's notes on the package, outside contributions to Swift Build are "welcomed and encouraged." The notes also mention that "to be a truly great community, Swift.org needs to welcome developers from all walks of life, with different backgrounds, and with a wide range of experience."

"A diverse and friendly community will have more great ideas, more unique perspectives, and produce more great code," according to the Swift development team. "We will work diligently to make the Swift community welcoming to everyone."

Apple's next Swift Student Challenge, intended to encourage young programmers to become fluent in Swift, opens on February 3. A total of 350 developers aged 13 or older will be picked as winners in various categories, with the top 50 being rewarded with a trip to Apple's Cupertino corporate campus.



3 Comments

applesauce007 18 Years · 1707 comments

Great news for the Swift community.
Apple says 

that open-sourcing Swift Build will encourage participation from the corporate sector, academia, and other open-source projects.
Swift's popularity should take off like a rocket for the awesome programming language that it is.

2 Likes · 1 Dislike
mattinoz 10 Years · 2543 comments

Great news for the Swift community.
Apple says that open-sourcing Swift Build will encourage participation from the corporate sector, academia, and other open-source projects.
Swift's popularity should take off like a rocket for the awesome programming language that it is.

It should help accelerate the embedded swift usage that has been experimented with in the last couple of years..

1 Like · 1 Dislike
michelb76 9 Years · 713 comments

Great news for the Swift community.
Apple says that open-sourcing Swift Build will encourage participation from the corporate sector, academia, and other open-source projects.
Swift's popularity should take off like a rocket for the awesome programming language that it is.

That depends on how Apple will stewart it. Many of the previous contributions and suggestions by the community have been shot down because Apple doesn't need it. It's gone from a simple, elegant language to a monstrosity since Lattner left. Some critiques: https://blog.jacobstechtavern.com/p/apple-is-killing-swift

Swift would be perfect if it wasn't dying a death by 1000 cuts thanks to the inherent conflict in its governance.

Swift is caught between two clans: the Swift Working Group™ open-source community, and the Apple corporate entity who pays most of their salaries. Both have their own incentives and their own imperfections, but you guess who has the majority influence.

Ridiculous, permanent, tech debt such as hardcoded compiler exceptions are permanently living in the compiler codebase. Even worse, half-baked concepts such as result builders are pushed through without any real discussion because Apple wants the SwiftUI syntax to look pretty.

It's an amazing language still, but I can't see it surviving as nicely in the next 10 years if Apple doesn't learn to let go.

3 Likes · 1 Dislike