I’ve been taking the Stanford CS193P building IOS apps in Swift course on Youtube of late, and the idea of doing my app as full stack Swift seems mighty appealing.
There’s a lot (for me) to like in the language - type safety, immutable data structures by default and a whole lot more, plus a syntax and level of abstraction I really enjoy working at.
For a while every time someone mentioned Swift a bunch of people would be “yeah, but then you have to use XCode” and go on to describe various crashes, bugs, and malfunctions that made Swift a pain to use. Have you had that experience at all?
Apple put a lot of work into XCode comparatively recently. I’ve not been using it full time but what I’ve done with it has been rock solid.
IMO what you can criticize XCode for is lacking the kind of polish and tooling Windows devs have come to expect from Visual Studio, but for what it does IMO XCode does it reasonably well.
I’ve been taking the Stanford CS193P building IOS apps in Swift course on Youtube of late, and the idea of doing my app as full stack Swift seems mighty appealing.
There’s a lot (for me) to like in the language - type safety, immutable data structures by default and a whole lot more, plus a syntax and level of abstraction I really enjoy working at.
For a while every time someone mentioned Swift a bunch of people would be “yeah, but then you have to use XCode” and go on to describe various crashes, bugs, and malfunctions that made Swift a pain to use. Have you had that experience at all?
Apple put a lot of work into XCode comparatively recently. I’ve not been using it full time but what I’ve done with it has been rock solid.
IMO what you can criticize XCode for is lacking the kind of polish and tooling Windows devs have come to expect from Visual Studio, but for what it does IMO XCode does it reasonably well.