People often suggest forking large projects like this, as if it would solve a problem. If you actually think through what that would entail, you'll find that it would actually create more problems.
The people that actually do the work on Swift are those that control the language and its destiny. You could fork it, but without a similar amount of effort behind your fork there's no way you can convince people to switch from the mainline.
i think a fork not owned by apple could gather a lot of developers interested in expanding the language to other platforms. it is initially a great language.
The people that actually do the work on Swift are those that control the language and its destiny. You could fork it, but without a similar amount of effort behind your fork there's no way you can convince people to switch from the mainline.