←back to thread

612 points dayanruben | 1 comments | | HN request time: 0s | source
Show context
picafrost ◴[] No.42900086[source]
Swift is a nice language. I'm glad to see it being released from the clutches of Apple. I can only imagine how large of a task this is. I hope some day to be able to use it. The last time I tried a cross-platform project with it I switched languages due to `URLSession.shared.data` (a network request) being unable to compile on Linux.
replies(1): >>42900326 #
isodev ◴[] No.42900326[source]
Is it really being released? Although some parts of the language and build chains are technically open source (as in, you can see the code), the project is still completely controlled by Apple at the top.
replies(3): >>42900476 #>>42901505 #>>42908104 #
st3fan ◴[] No.42901505[source]
You are wrong about "some parts" - you can browse github.com/swiftlang to find out.

About control - serious question: how is this different from for example Rust, Go, Zig or Python? For each of those you can submit a change proposal through an official process and you can submit code changes through a pull request.

But also for each of those there is a non-zero chance that a smaller group of people who do governance of the project, the core team or leads or module owners, will either tell you that your proposal or code change is not appropriate or compatible with the project's goals or they will help you to merge it. That is exactly the same for Swift.

Why is Apple suddenly a dictator while every other project also has an agenda and strict rules that are being enforced?

Is the expectation to just be able to do whatever you want in a project like Swift?

replies(4): >>42901588 #>>42901603 #>>42901886 #>>42905297 #
isodev ◴[] No.42901886{3}[source]
You’re only focusing on access to source code, the comment is about leadership and decision making. Remember the OmniSharp story around VSCode from just two years ago? It’s a very high profile example of what can (and eventually will) happen with corporate-controlled projects.

Swift can’t evolve or even exist without Apple and so unless you’re Apple, then Swift is too great of a risk.

replies(1): >>42902035 #
1. chefandy ◴[] No.42902035{4}[source]
> Swift can’t evolve or even exist without Apple and so unless you’re Apple, then Swift is too great of a risk.

I'm not sure what you're saying here. It's Apache licensed so you can just fork it. It's got pretty active development and a whole lot of software developers that use it-- if Apple decides to somehow lock down the repo and stop accepting PRs, what's stopping a group of developers from just making their own branch? It's got non-Apple cross-platform GUI frameworks, good support in editors... Sure it's 100% not as good off of Apple systems but I'm not sure what they'd be expected to do MORE than open it up with an Apache license?

And OmniSharp works just fine in VSCode from what I see. What am I missing?