cyberzombie

This sounds exactly like what I've been hoping for - to setup Swift up as a viable middle tier product. It's got a couple of years to go before I'd suggest new development not be done in Java, but this is a big step.

The enterprise developer in me is cheering.

freerange said:

Non-programmer asks, "does making Swift open source create / increase future security risks / problems"? 

Yes and no. It potentially surfaces security risks earlier. But it also provides a huge pool of talent to find/review/correct those situations. Also, Swift is not the OS - it is a language. It isn't so much security issues as it is buffer overruns and other memory shenanigans - which Swift is designed to make inaccessible. Most security issues would IMO be from linking in libraries/frameworks written in C/C++/Objective C...

None of the above. I got a $100 Apple Store card, which I will be putting toward a Milanese loop for my Apple Watch.