+1 works great
Definitely Swift. But: 1) If you plan to develop a SDK/lib compatible with both Obj-C and Swift and don't want to adapt to new Swift changes coming forward or 2) You absolutely can't stand SourceKit related bugs in…
worth watching?
This was actually really impressing
Second that. This is what still keeps me at AWS.
+1 works great
Definitely Swift. But: 1) If you plan to develop a SDK/lib compatible with both Obj-C and Swift and don't want to adapt to new Swift changes coming forward or 2) You absolutely can't stand SourceKit related bugs in…
worth watching?
This was actually really impressing
Second that. This is what still keeps me at AWS.