This was my reaction to that comment, too. Swift is a strongly typed language, it just infers the type at compile time so the programmer doesn't have to manually enter it when declaring the variable. Considering it also differentiates between variables which can contain "nil" and ones that can't in its type system, I'd say it's one of the most strongly typed languages in common use, so I don't understand the statement.
The one platform thing is a bummer, but it's changing pretty fast right now so I don't blame Apple for not wanting to lock any decisions in with third parties yet. I hope they add it to their pile of open source projects before too long, though. Considering the reference implementation is LLVM-based, it shouldn't be hard for it to become very portable very fast.
(Besides, who doesn't like a language which has the entire unicode character set available for variable names, including the symbols? Can make for some colorful code.)