Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Open Source IOS Iphone Operating Systems Programming Software Ubuntu Apple News Build Technology

Apple Releases First Preview of Swift 3.0 ( 227

DaGoatSpanka quotes a report from MacRumors: Apple yesterday released the first preview build of Swift 3.0, a major update to Apple's open source Swift programming language. Swift 3.0's official release is expected to come in late 2016 after proposed changes are finalized. The Swift 3.0 preview can be downloaded from the official Swift website. There are versions of Swift 3.0 available for Xcode 7.2, Ubuntu 14.04, and Ubuntu 15.10. [Swift 3.0 is not source compatible with Swift 2.2 as it introduces source-breaking changes, but going forward, the goal is to make Swift 3.0 source compatible with future Swift language updates.] Swift 3.0 will likely be shown at Apple's upcoming Worldwide Developers Conference (WWDC).
This discussion has been archived. No new comments can be posted.

Apple Releases First Preview of Swift 3.0

Comments Filter:
  • by Anonymous Coward on Thursday June 02, 2016 @09:04AM (#52232053)

    Last release broke for loops, what was broken now? If statements??

    • by pushing-robot ( 1037830 ) on Thursday June 02, 2016 @09:23AM (#52232159)

      No, function calls.

      https://www.hackingwithswift.c... []

      Yes, it'll make code shorter and simpler, but renaming most library methods is still a kick in the teeth to developers.

      • What a fucking disaster. I like swift a lot more than ObjC, but this shit is insane.
        • by hawkbug ( 94280 )

          I agree. Every damn time they update Xcode, I'm having to refactor code. This is bullshit.

      • by Beezlebub33 ( 1220368 ) on Thursday June 02, 2016 @09:37AM (#52232253)

        And enums, apparently.

        I understand having it consistent (which is their argument for the changes), but this just means that they they screwed it up in 1 and 2. Seriously, you change naming conventions from UpperCamelCase to lowerCamelCase? Now? That's the sort of decision that should be made (with reasons) when you are designing the language the first time; and then you have a group of really nitpicky, anal-retentive types go through the language to check for all the inconsistencies, and then you fix them, and then you release it. This whole thing screams amateur hour; yeah, I understand it a little more when python says 'oops, we messed up because there was a single guy who designed the language, and he didn't have a team behind him'. However, this is frigging Apple, and they have lots of people and money, and Swift was (I hope??) intended from pretty early on to be where people were going to go, so it should have been done right the first time or two.

        • by pushing-robot ( 1037830 ) on Thursday June 02, 2016 @10:08AM (#52232441)

          Swift inherited this mess from Objective-C. The Swift team stuck with the old conventions for a while to make the transition easier, but now they want to shed the ugly bits and move forward. I'm not sure there's a better way they could have handled this, to be honest. Everything has tradeoffs.

        • I'm not aware of any good programming language that never required any revision. So you are basically holding Apple to a standard that noone else has ever met before...

          But hey, if it makes you feel better about your own miserable life to complain on the internet...

          • by bondsbw ( 888959 )

            The set of things classified as a "revision" is obviously a superset of things classified as "breaking change". If you stay out of the "breaking change" category (e.g. only new syntax that did not previously compile) then it isn't a problem.

            Yes, there are plenty of language updates which do not break existing code. When they do, many language design teams strive to limit any breaking changes to concepts that are only used by a very small number of people, or bugs which result in undocumented behaviors tha

      • by Maury Markowitz ( 452832 ) on Thursday June 02, 2016 @10:14AM (#52232471) Homepage

        Clearly all the people complaining don't actually use Swift for production code and/or just like to complain.

        I converted my antenna modelling project to 3.0 in about three minutes. Most of this was due to the new selector syntax, which I had to spend time looking up on Stackoverflow. The rest was trivial, and my code is cleaner and shorter than ever.

  • by sproketboy ( 608031 ) on Thursday June 02, 2016 @10:09AM (#52232447)

    But that's not saying much...

  • Because apparently their engineers lack the ability to think far enough ahead to design something that lasts longer than a single coding cycle.
  • by __aaclcg7560 ( 824291 ) on Thursday June 02, 2016 @10:35AM (#52232593)
    Seriously, Apple, where's the love?
  • Is anybody going to bite on a new proprietary language? Have we not learned anything from what Oracle has done with Java?

In order to get a loan you must first prove you don't need it.