3 ms·

The reason you are getting downvoted (I believe) is that you are posing a false dilemma.[1] It is not the case that Apple is most likely going to leave Swift cl

The reason you are getting downvoted (I believe) is that you are posing a false dilemma.[1] It is not the case that Apple is most likely going to leave Swift closed source based on the evidence that we've seen. ALL the evidence we have, as far as swift goes, is that they haven't decided yet, according to Chris' email quote. As others have said, most of Apple's other programming language work has become open source, and I would say that evidence is much stronger than the "evidence" (really lack of evidence one way or the other) that they are going to leave it closed source. [1] http://en.wikipedia.org/wiki/False_dilemma http://en.wikipedia.org/wiki/False_dilemma

chc 12y ago
> ALL the evidence we have, as far as swift goes, is that they haven't decided yet, according to Chris' email quote. Yes, precisely. Apple currently has no intention of open-sourcing Swift. All of the evidence supports precisely what I've been saying. This is why I think it is good to remind them that we want them to decide in the affirmative.
- 3JPLW 12y ago
  You're picking a pretty fine nit on the meaning of the word 'intention.' I see your point, with the exception that you don't know what Apple's intentions are. We have a few pointers, though. The fact that Chris Lattner and some on his team are interested in open-sourcing it is a good sign. Given his wording, I would even say that he intends to have a discussion about open sourcing it. We have even less evidence that Apple intends to leave Swift forever closed source — it's simply the status quo. Apple, as a corporate entity, likely has no intention either way right now. Even if it did, Apple rarely broadcasts its intentions. Swift will likely be closed source until suddenly it's not.
  - chc 12y ago
    They don't need to intend to keep Swift closed forever in order for it to be kept closed forever. It takes an active intention for them to open it up, but not to keep it closed. If they put off making a final decision until the heat death of the universe, it will still never be open-sourced without them ever specifically intending not to.

chc 12y ago

> ALL the evidence we have, as far as swift goes, is that they haven't decided yet, according to Chris' email quote. Yes, precisely. Apple currently has no intention of open-sourcing Swift. All of the evidence supports precisely what I've been saying. This is why I think it is good to remind them that we want them to decide in the affirmative.

3JPLW 12y ago
You're picking a pretty fine nit on the meaning of the word 'intention.' I see your point, with the exception that you don't know what Apple's intentions are. We have a few pointers, though. The fact that Chris Lattner and some on his team are interested in open-sourcing it is a good sign. Given his wording, I would even say that he intends to have a discussion about open sourcing it. We have even less evidence that Apple intends to leave Swift forever closed source — it's simply the status quo. Apple, as a corporate entity, likely has no intention either way right now. Even if it did, Apple rarely broadcasts its intentions. Swift will likely be closed source until suddenly it's not.
- chc 12y ago
  They don't need to intend to keep Swift closed forever in order for it to be kept closed forever. It takes an active intention for them to open it up, but not to keep it closed. If they put off making a final decision until the heat death of the universe, it will still never be open-sourced without them ever specifically intending not to.