I agree 100% with you on Objective-C. I really do like it. And I've been struggling to build libobjc2.a for 68k Amigas. My biggest fear with Swift is that they'll eventually migrate off of Objective-C which would effectively kill the language. Bloodline, if you're interested in helping port libobjc2.a let me know; there are some things there that are over my head.
Back on topic, I think as long as both languages are supported I'm good with Swift and I basically feel the same as you, again. There is a weird sense of detachment involved when looking at and working with Swift. I kinda feel like I don't know exactly how to get there from here, sometimes.
I'm surprised there weren't many references to it's similarity to JavaScript as well. I'm probably in the minority here insofar as I also love JavaScript as a language, outside of the browser. There are some syntax bits I'd like to see in JS, and they are slowing appearing over time. I also like it in the browser, but only because I know it very well.
To be fair you are still allowed to use semicolons as stamement terminators... My biggest gripes are;
The bizzare function definition syntax.
The odd variable/constant type placement (though, they didn't have much choice)
The method calling feels clunky (Obj-C looks weird but is actually rather elegant*)
Due to the unfamiliar nature of the syntax, as someone coming from C, class definitions appear almost random in swift.
My confident, and probably inaccurate, prediction for the future is that Swift will be picked up by beginners and a few hobbyists... But serious developers will stick to Obj-C/C++ since they know it and will almost certainly be working in other C derived languages on other platforms/projects... Swift will then be silently dropped and remembered as an interesting little experiment 
* I think C++ gets it right as methods are sort of functions in a struct and Obj-C gets it right as methods are executed in response to a message. Both beautiful implementations of their object models!
