Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Swift 3.0 Released

swift.org

Post reply on HN
Print view View original

81–90 of 95 posts

Re: Swift 3.0 Released

#81

Post by LeoNatan25 »

kybernetyk wrote: post #47
dep_b wrote: 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

Isn't the sandbox only enabled if System Integrity Protection is enabled? Disable that and the plugins should work, if they are updated for Xcode 8.

[Update] Hmm, seems so. See this: https://github.com/inket/update_xcode_plugins

Re: Swift 3.0 Released

#82

Post by mminer »

justsaysmthng wrote: post #75
mrsteveman1 wrote: post #56

Earlier quoted context omitted.

> In the meantime, I'm thinking of reverting to Xcode 7.3 and running the two versions side by side... Is that possible ? I think you're probably better off just keeping Xcode 8 by itself, but use Swift 2.3 for projects if you need to. There are very very few differences between 2.2 and 2.3, converting existing code over is much faster than 2.2 -> 3.0.

Tried that, but it seems the build setting now needs an explicit SWIFT_VERSION configured .. And carthage dependencies don't have that so the build fails. Basically, I couldn't get my carthage dependencies to compile with Swift 2.3, so I went the Swift3 route, which now, after 10 hours wasted, was such a bad idea! Appstore was bugging me to update Xcode so I caved in and now I'm stuck with a project that doesn't buil…

To placate Carthage dependencies that complain about a missing SWIFT_VERSION configuration, try setting the TOOLCHAINS environment variable.

  TOOLCHAINS=com.apple.dt.toolchain.Swift_2_3 carthage bootstrap

Re: Swift 3.0 Released

#83

Post by osolo »

kybernetyk wrote: post #47
dep_b wrote: 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

Try this plugin[1] which will unsign Xcode and allows older plugins to work.

I also encourage you to file a radar [2] to let Apple know you're not pleased about them killing a thriving plugin ecosystem. Yes, I know there's a new plugin API but it's so crippled that 90% of the plugins on Alcatraz couldn't possibly move to it. If enough of us complain maybe they will listen.

[1] - https://github.com/nrbrook/MakeXcodePluginsWork

[2] - https://bugreport.apple.com/

Re: Swift 3.0 Released

#85

Post by st3v3r »

timjver wrote: post #66
sswezey wrote: post #63

I really wish Swift releases were not pinned to Apple releases. Swift 3 introduced several regressions and instead of prioritizing some serious regressions, they focused on swift evolution proposals. For example, one accepted proposal renamed the common array _flatten_ method to _joined_ because it aligned one use case. Granted this is low hanging fruit, but a whole bunch of low hanging fruit takes time away from ser…

The renaming of flatten to joined was a last-minute proposal, and it wasn't even implemented by someone of Swift's core team. I don't think it distracted the team much at all. Also, breaking changes such as this one were a lot easier to make in Swift 3 than in a later version.

If they're still making breaking changes like this, then why have they declared version 1? They should still be on version 0.x

Re: Swift 3.0 Released

#86

Post by ZenoArrow »

knocte wrote: post #71
awzurn wrote: post #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.

It's a matter of taste. As for me, that I tinkle more with .NET, I see their (Swift's) grass greener in the fact that they are not afraid of making breaking changes if they truly benefit the platform, something which I don't see MS doing anytime soon.

> " in the fact that they are not afraid of making breaking changes if they truly benefit the platform, something which I don't see MS doing anytime soon."

MS have made plenty of big changes recently, .NET Core being a prime example.

Re: Swift 3.0 Released

#87

Post by justsaysmthng »

mminer wrote: post #82
justsaysmthng wrote: post #75

Earlier quoted context omitted.

Tried that, but it seems the build setting now needs an explicit SWIFT_VERSION configured .. And carthage dependencies don't have that so the build fails. Basically, I couldn't get my carthage dependencies to compile with Swift 2.3, so I went the Swift3 route, which now, after 10 hours wasted, was such a bad idea! Appstore was bugging me to update Xcode so I caved in and now I'm stuck with a project that doesn't buil…

To placate Carthage dependencies that complain about a missing SWIFT_VERSION configuration, try setting the TOOLCHAINS environment variable. TOOLCHAINS=com.apple.dt.toolchain.Swift_2_3 carthage bootstrap

This is the thing I've been looking for !

Thank you for the 63 characters of wisdom, my project now builds !

Re: Swift 3.0 Released

#88

Post by armadsen »

untog wrote: post #36
nicky0 wrote: 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.

A lot of this is worse for Swift than it is for Objective-C. Still, I do find it weird that such a mature product (roots going back decades, really) is still so shaky in fundamental areas. In many ways it has actually regressed since e.g. version 3.

Re: Swift 3.0 Released

#89

Post by knocte »

ZenoArrow wrote: post #86
knocte wrote: post #71

Earlier quoted context omitted.

It's a matter of taste. As for me, that I tinkle more with .NET, I see their (Swift's) grass greener in the fact that they are not afraid of making breaking changes if they truly benefit the platform, something which I don't see MS doing anytime soon.

> " in the fact that they are not afraid of making breaking changes if they truly benefit the platform, something which I don't see MS doing anytime soon." MS have made plenty of big changes recently, .NET Core being a prime example.

I was talking about languages.
Post reply on HN