Live data from Hacker News

Swift 3.0 Released

swift.org

41–50 of 95 posts

Re: Swift 3.0 Released

#41
post #29

Earlier quoted context omitted.

It won't happen because Apple won't give you the option. Swift 3.x has a large amount of syntax changes. The compiler helps with the refactoring but it's still work.

> It won't happen because Apple won't give you the option. What won't happen, havoc in the ecosystem? How is Apple relevant? > Swift 3.x has a large amount of syntax changes. Yes? > The compiler helps with the refactoring but it's still work. That's not what I'm talking about. A bit of drudge work is fine, the issue of the Python transition is that you get usually hard to debug runtime failures down the line, possibl…

What won't happen is that Apple won't let people build against old versions of Swift. We'll all be on 3.x soon.

I have no idea how hard the conversion of a large Python 2 to 3 project is. My projects were small and I had no troubles. At any rate 2020 will be here soon and 2.x support will end. All Swift users will be on 6.x by then.

Re: Swift 3.0 Released

#42

Wow, they've basically renamed the entire Standard Library, see the changeset: https://github.com/apple/swift-evolution/blob/master/proposa... Not that I mind though. This kind of thing should be easy to auto refactor.

Yes, not really a problem in that case. But let's not forget that this release also contains nearly 50 other source breaking swift-evolution proposals (full changelog here: https://github.com/apple/swift/blob/master/CHANGELOG.md).

But one of the things I like about how the language is begin developed is that everyone involved is aware that having the language in a constant state of flux is painful, and try to provide useful warning messages (or wizards if you use XCode) for those that will need to update their code to a newer release sooner or later.

Re: Swift 3.0 Released

#43
post #36
post #31

Earlier quoted context omitted.

I don't want to have to ship apps containing the entire runtime. I'm waiting for the stable ABI. As well, I'm happy to let the keen early-adopters be the guinea pigs. Xcode 8 only came out today. If you have production apps, it's madness to upgrade on day one. I'll wait a few weeks/months for the remaining bugs to shake out. Don't get me wrong I'm very pro-Swift. But I'm also mindful of my time and sanity. Switching…

I've only recently gotten into iOS development and the state of XCode amazes me. It's awful. Frequent crashes, disappearing tests, syntax highlight shutting down... it really makes me wish there were an alternative.

There's nothing stopping you from using one. The great thing about OSX is that you can get to the command line just like Linux and use Emacs or Vim. Or even GUI IDEs like Geany if that's what you want.

Re: Swift 3.0 Released

#44
post #36
post #31

Earlier quoted context omitted.

I don't want to have to ship apps containing the entire runtime. I'm waiting for the stable ABI. As well, I'm happy to let the keen early-adopters be the guinea pigs. Xcode 8 only came out today. If you have production apps, it's madness to upgrade on day one. I'll wait a few weeks/months for the remaining bugs to shake out. Don't get me wrong I'm very pro-Swift. But I'm also mindful of my time and sanity. Switching…

I've only recently gotten into iOS development and the state of XCode amazes me. It's awful. Frequent crashes, disappearing tests, syntax highlight shutting down... it really makes me wish there were an alternative.

You can buy AppCode. It's based on IntelliJ, so if you are used to taht it's great. But it's not perfect and I usually have both IDEs open when working on iOS (in aprticular, running and debugging are nicer from XCode. I write my code in AppCode and run it from XCode).

Re: Swift 3.0 Released

#45

Wow, they've basically renamed the entire Standard Library, see the changeset: https://github.com/apple/swift-evolution/blob/master/proposa... Not that I mind though. This kind of thing should be easy to auto refactor.

I don't mind either. And I have a commercial Mac application written 98% in Swift to maintain.

Now the risks were known when we green fielded the project. It was certain that Swift syntax and the frameworks would change in the future. But the time we saved in development makes up many times for the maintenance burden now.

Luckily refactoring strongly static typed code is not that of a fiasco :)

Re: Swift 3.0 Released

#47
post #39

Swift 3.0 is really nice but I backtracked out of Xcode 8.0 for now. I am used to Xcode but this one still vomits Apple internal debug messages into the console, that's really too rough for me. I'll wait for the .01 or the .1 before upgrading all my projects. Funny thing is I downloaded one of the first if not the first beta of Xcode 8 and it already migrated my projects flawlessly (where possible). It's all the othe…

I hope I can get used to work without the Polychromatic plugin[1]. Or that the dev somehow can get around the new plugin sandbox in Xcode.

Haven't tested it yet with Xcode 8 but I fear it won't work.

[1] - https://github.com/kolinkrewinkel/Polychromatic

Re: Swift 3.0 Released

#49
Can't wait for the day when they're done deciding to only make major releases every year, and actually settle on a common syntax and platform for the language, will be great not having to worry about my source code blowing up...

... then again, seeing some actual refactor support in Xcode would be pretty great too, but you can't wish for too much at once.

Re: Swift 3.0 Released

#50
If you're thinking of updating to Xcode 8, hoping that your project will 'just build', don't get your hopes too high.

I've already spent all day fixing, updating, searching around for all kinds of errors that the build system throws at me. It also required me to update the project dependencies to their latest versions which support swift 3/xcode 8. Some dependencies (like SwiftBond 5) have changed a lot and now my project has hundreds of syntax errors due to renamed methods, not that hard to fix, but not sure if they'll still run the same...

So this is a major upgrade to your project - do it when you have spare time to waste.

In the meantime, I'm thinking of reverting to Xcode 7.3 and running the two versions side by side... Is that possible ?

Post reply on HN