3 ms·

Can the OP tell us anything about building their Twitter framework in Swift. Any gotchas or problems they came across building it? Is Swift ready for the primet

Can the OP tell us anything about building their Twitter framework in Swift. Any gotchas or problems they came across building it? Is Swift ready for the primetime. Should I start switching all my apps to Swift ASAP? Otherwise I'm just starting at code in a language I can hardly read.

jmduke 12y ago
I'm rewriting one of my apps in Swift and I'm enjoying it a lot, but it's definitely a bumpy road. You're dealing with both a beta IDE and a beta language, and you have to get used to a myriad of errors, some of which are indecipherable (arcane things like issues iterating over an array or Optional behavior that doesn't mesh with documentation/templates). Still, Swift is a joy to program in compared to Objective-C (at least IMHO) and its giving me the chance to re-architect a very poorly planned v1.0, so that alone is worth the trouble. I think it's a good idea if you're very interested in learning Swift, but not really worth doing for its own sake.
mattdonnelly 12y ago
Most of problems I encountered while writing this came from Swift's interoperability with Objective-C. It can often be difficult to work with and takes a while to get used to. I actually think it would be worth developers considering porting their existing Objective-C libraries to Swift for this reason alone. That said, I don't think developers should start porting their App Store apps yet. It still feels very much like it's in beta and some functionality hasn't been implemented (such as static class variables). Despite this though, I think Swift has a huge amount of potential, and once things really kick off with it, we'll probably be seeing a lot more developers writing apps in Swift than in Objective-C. The language really has a lot to offer over Objective-C in my opinion PS: hi kevin
- sAuronas 12y ago
  I thought I was imagining the static class problem...the documentation, while well-written, leaves much to be desired, especially for the above-mentioned. I've enjoyed writing in Swift so far but the playground crashes often. Xcode has not yet, so that has helped.

jmduke 12y ago

I'm rewriting one of my apps in Swift and I'm enjoying it a lot, but it's definitely a bumpy road. You're dealing with both a beta IDE and a beta language, and you have to get used to a myriad of errors, some of which are indecipherable (arcane things like issues iterating over an array or Optional behavior that doesn't mesh with documentation/templates). Still, Swift is a joy to program in compared to Objective-C (at least IMHO) and its giving me the chance to re-architect a very poorly planned v1.0, so that alone is worth the trouble. I think it's a good idea if you're very interested in learning Swift, but not really worth doing for its own sake.

mattdonnelly 12y ago

Most of problems I encountered while writing this came from Swift's interoperability with Objective-C. It can often be difficult to work with and takes a while to get used to. I actually think it would be worth developers considering porting their existing Objective-C libraries to Swift for this reason alone. That said, I don't think developers should start porting their App Store apps yet. It still feels very much like it's in beta and some functionality hasn't been implemented (such as static class variables). Despite this though, I think Swift has a huge amount of potential, and once things really kick off with it, we'll probably be seeing a lot more developers writing apps in Swift than in Objective-C. The language really has a lot to offer over Objective-C in my opinion PS: hi kevin

sAuronas 12y ago
I thought I was imagining the static class problem...the documentation, while well-written, leaves much to be desired, especially for the above-mentioned. I've enjoyed writing in Swift so far but the playground crashes often. Xcode has not yet, so that has helped.