Re:Why Greet Apple's Swift 2.0 With Open Arms?
by coldtea on Thursday June 18, 2015 @04:41PM
(#9741496)
>Imagine Swift becomes a wild success; everyone's writing everything in Swift. What will your reaction be when Apple again makes a "legitimate business decision" and leverages the success to the benefit of their company and implicitly disadvantages other platforms? Maybe they double up on Swift support on Mac and start shipping additional features first for LLVM/Clang on OSX. Will you brush it off again as an understandable move by Apple?
So? It sounds not only an understandable move, but NO ISSUE at all.
In this scenario you describe people have ALREADY benefited tremendously from Swift ("writing everything in it" etc, as you describe).
If they don't like some Apple's moves they can always fork from that point. A language in which "they have written everything", means it has huge adoption, and several third party companies and lots of community members to take this up.
And even if they don't fork, they still have the existing compiler and libraries -- the ones they LIKED so much in you scenario that they have adopted and written everything in them --, and they can continue using them.
Basically your argument is: if Apple gives this as Open Source, they should continue giving us anything they do with it as Open Source.
For me just giving it once as Open Source is enough.
If the main offering is good enough, then I don't care if they add some proprietary extensions, now or in 2020.
And if the main offering is not good, I don't care about it in the first place, whether OSS or not.
So? It sounds not only an understandable move, but NO ISSUE at all.
In this scenario you describe people have ALREADY benefited tremendously from Swift ("writing everything in it" etc, as you describe).
If they don't like some Apple's moves they can always fork from that point. A language in which "they have written everything", means it has huge adoption, and several third party companies and lots of community members to take this up.
And even if they don't fork, they still have the existing compiler and libraries -- the ones they LIKED so much in you scenario that they have adopted and written everything in them --, and they can continue using them.
Basically your argument is: if Apple gives this as Open Source, they should continue giving us anything they do with it as Open Source.
For me just giving it once as Open Source is enough.
If the main offering is good enough, then I don't care if they add some proprietary extensions, now or in 2020.
And if the main offering is not good, I don't care about it in the first place, whether OSS or not.