3 ms·

Which version (Swift 2, 3 or 4)?

by themihai 10y ago

BanzaiTokyo 10y ago
The article is talking about version 3.0
- themihai 10y ago
  I see.. though it(swift 3) was just released. I didn't know the enterprise world changed so much(i.e. adopting a technology immediately after release). The core/std library `is not yet ready for production use, and in fact are still in the earliest stages of development.` I also heard Swift 4 is likely to have breaking changes. (ABI) stability will start only on Swift 4 too. But what do I know...? Swift is great and everyone should abandon whatever obsolete language/tools they have in favour of this shinning thing because it has a nicer syntax.
melling 10y ago
Swift 3 is the version with large source change. It required a lot of refactoring. Fortunately, many of the fixes were handled automatically by Xcode. I'm keeping a list of changes: https://h4labs.wordpress.com/2016/09/17/my-ios-10-and-swift-3-refactor-list/ https://h4labs.wordpress.com/2016/09/17/my-ios-10-and-swift-... Any breaking changes going forward should be much less. Of course, you might be in the camp that wants zero breaking changes, then Swift probably isn't for you.
- themihai 10y ago
  Do you really think Swift 3 is ready for enterprise usage? They say the core lib is not ready yet for production usage[0]. It's not about how may breaking changes I'm willing to take but in the enterprise world there is little incentive to rewrite large code bases. Even in the start-up environment the more code you write the less excited you are about breaking changes. Also Xcode doesn't run on Linux or windows and last time I've checked MacOS was not the the OS of choice in the enterprise world so Xcode is not an option. Next claim I'm expecting is that Swift is ready for the InSight Mars lander mission. [0] https://swift.org/core-libraries/ https://swift.org/core-libraries/
  - melling 10y ago
    I haven't used Swift on the server yet, so I can't honestly say. I'll give it a try soon. However, it's probably best for devs who are already using it for apps (code reuse, experience, etc). For other dev, I might try Elixir, for example, for web dev. It is gaining a lot of momentum. A critical mass in adoption means better support, quicker answers to questions, etc. We all can't pay IBM to worry about the details.

Which version (Swift 2, 3 or 4)?

BanzaiTokyo 10y ago

The article is talking about version 3.0

themihai 10y ago
I see.. though it(swift 3) was just released. I didn't know the enterprise world changed so much(i.e. adopting a technology immediately after release). The core/std library `is not yet ready for production use, and in fact are still in the earliest stages of development.` I also heard Swift 4 is likely to have breaking changes. (ABI) stability will start only on Swift 4 too. But what do I know...? Swift is great and everyone should abandon whatever obsolete language/tools they have in favour of this shinning thing because it has a nicer syntax.

melling 10y ago

Swift 3 is the version with large source change. It required a lot of refactoring. Fortunately, many of the fixes were handled automatically by Xcode. I'm keeping a list of changes: https://h4labs.wordpress.com/2016/09/17/my-ios-10-and-swift-3-refactor-list/ https://h4labs.wordpress.com/2016/09/17/my-ios-10-and-swift-... Any breaking changes going forward should be much less. Of course, you might be in the camp that wants zero breaking changes, then Swift probably isn't for you.

themihai 10y ago
Do you really think Swift 3 is ready for enterprise usage? They say the core lib is not ready yet for production usage[0]. It's not about how may breaking changes I'm willing to take but in the enterprise world there is little incentive to rewrite large code bases. Even in the start-up environment the more code you write the less excited you are about breaking changes. Also Xcode doesn't run on Linux or windows and last time I've checked MacOS was not the the OS of choice in the enterprise world so Xcode is not an option. Next claim I'm expecting is that Swift is ready for the InSight Mars lander mission. [0] https://swift.org/core-libraries/ https://swift.org/core-libraries/
- melling 10y ago
  I haven't used Swift on the server yet, so I can't honestly say. I'll give it a try soon. However, it's probably best for devs who are already using it for apps (code reuse, experience, etc). For other dev, I might try Elixir, for example, for web dev. It is gaining a lot of momentum. A critical mass in adoption means better support, quicker answers to questions, etc. We all can't pay IBM to worry about the details.