Wow, the OP loves jumping to conclusions. I've seen on HN a couple of threads where people claim that Apple employees say they, at a minimum, need to clean up

Wow, the OP loves jumping to conclusions. I've seen on HN a couple of threads where people claim that Apple employees say they, at a minimum, need to clean up the codebase first before open sourcing the language. While I don't know if that's true, I'm prepared to wait until Apple, not this guy, says that Swift will or will not be open sourced. Just because it's not open source now doesn't mean it'll never be. Then they point out that there are 3rd party HTTP libraries, and completely ignore the possibility that maybe Swift might be just the thing to catalyze the creation of a new one. To be sure, unless you're serving from an OS X based server, it'll be hard to deploy Swift-based apps until significant supporting infrastructure has been built. But I don't see any real evidence that "never" is the answer to "When Can I Code Swift on the Server?"