Aren't they probably just holding off on open sourcing it until...it's finished. I know they've just shipped '1.0' but I think they're still making pretty big changes.
Hard to say with Apple. Their record on openness and transparency isn't great. This would be akin to Microsoft open sourcing Visual Basic. Seeing Swift released would make my and a whole lot of other people's days, but honestly? I wouldn't hold my breath.
Introducing Phoenix, Swift set free
41–50 of 122 posts
Re: Introducing Phoenix, Swift set free
#42Interesting it seems to be more about building an open version of the iPhone called 'stratosphere' (see this https://source.ind.ie/project/ind-ie/blob/master/source/inde... ) Given that Apple went all patent troll on Google's Android licensees and patents, unlike copyrights, cannot be avoided by re-expression, I'm wondering about the strategy of making an open phone. Easily doable in 20 years (post patent expiration)…
I think "stratosphere" is the Cloud platform. The phone from AFAIK is Indie Phone.
Re: Introducing Phoenix, Swift set free
#43Earlier quoted context omitted.
Nobody at Apple has expressed any intention to make Swift free. Zero. Zip. You might call this "out of character," but the actual actions that they've taken in the real world have been to make Swift proprietary and turn away requests to open it up. Those are the facts, not a "boogeyman."
This is false. > "You can imagine that many of us want [Swift] to be open source and part of llvm, but the discussion hasn't happened yet, and won't for some time." - Chris Lattner, LLVMDev mailing list. http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-June/073698....
Re: Introducing Phoenix, Swift set free
#44Actually, having spoken with Swift team in Apple (rather not mention their names in case they get in trouble) on this topic, they seemed to be happy opening it up in general and opening it up as a general purpose language. Swift could ultimately replace C++ as the language of choice for game development and more.
That said, IMHO, the language will progress a lot faster initially if it's driven by a single master than to be pulled into many directions.
Re: Introducing Phoenix, Swift set free
#45I really don't get why people stress over this. Swift only has value with the Mac OS X and iOS ecosystems, specially as a mean to drag Objective-C developers into the FP world. There are so many open source languages in the ML family, a few of them are even used in the industry for several years now. Just go and join one of those projects. They will appreciate any help they can get.
And .NET only had value in the MS world before Mono which very popular.
Re: Introducing Phoenix, Swift set free
#46They should really come up with a better name. Phoenix is over used and even in open-source has a long history http://en.wikipedia.org/wiki/Firefox
Re: Introducing Phoenix, Swift set free
#47If any of you want to help out, please do get in touch.
Ideally, of course, if Apple opens Swift up, we can contribute to that instead of duplicating effort :)
Re: Introducing Phoenix, Swift set free
#48Aren't they probably just holding off on open sourcing it until...it's finished. I know they've just shipped '1.0' but I think they're still making pretty big changes.
Re: Introducing Phoenix, Swift set free
#49I really don't get why people stress over this. Swift only has value with the Mac OS X and iOS ecosystems, specially as a mean to drag Objective-C developers into the FP world. There are so many open source languages in the ML family, a few of them are even used in the industry for several years now. Just go and join one of those projects. They will appreciate any help they can get.
Re: Introducing Phoenix, Swift set free
#50Earlier quoted context omitted.
Welp. When I did some cursory googling for "visual basic open source", that page wasn't anywhere on my results. Now I feel like a fool. I'd still be very surprised if Swift got the same treatment. It just doesn't seem like a very Apple-ey thing to do.
Apple has historically been pretty open at this level. Open sourcing, say, UIKit would be a shocking move on their part, but I'd argue that not eventually open-sourcing the Swift compiler would be equally shocking. For example, they've kept their LLVM contributions open source even though they wouldn't have to, they developed clang in the open, they released their ARM64 LLVM backend, and they've open sourced various…