> "But I don't see the libraries and modules being there to allow most devs to just switch right away."
Obj-C libraries have interfaces auto-translated to Swift, so barring some edge cases are already entirely usable.
Writing a Swift app isn't a problem right now because of lack of library support, but mostly because the compiler still likes to segfault and taunt you. Frequently.
Either way, I like the language, I've been working with it for the past month, and it's neat and brings a bunch of really nice concepts to the table.
But "remake computer programming"? Wut.
Swift will quickly become the standard for OSX and iOS code, but that is but a tiny corner of programming-dom.
Obj-C libraries have interfaces auto-translated to Swift, so barring some edge cases are already entirely usable.
Writing a Swift app isn't a problem right now because of lack of library support, but mostly because the compiler still likes to segfault and taunt you. Frequently.
Either way, I like the language, I've been working with it for the past month, and it's neat and brings a bunch of really nice concepts to the table.
But "remake computer programming"? Wut.
Swift will quickly become the standard for OSX and iOS code, but that is but a tiny corner of programming-dom.