BUT: The standard library is very sparse. The reference documentation of the swift standard library is only about 50 pages, most things are missing.
So you have to fall back to the the Objective C runtime, in order to get something done. The automatic binding is fine, but there is so much friction between the layers, that all the fine parts of swift -- safety, expressiveness, automatic memory handling -- are covered in the end.
Apple has still a long way to go in order to implement a standard environment, which is safe and fun to use.
- If you cannot read a file in memory (because it is too big), you have to fall back to C or have to implement buffering itself. Memory Handling?
- No Exception handling (only a "Runtime Exception", which is very dubious how to catch). Having to check every invocation is not state of the Art. Expressiveness?
- You need references in order to handle error pointer. Type safety?
- For simple HTTP I/O you have either to use and understand this syntactic mess by heart, http://stackoverflow.com/questions/24016142/how-to-make-an-http-request-in-swift
or you have to dig into tons of information about a specific delegate. Fucking block syntax?!