Debug 42: Swift roundtable

Debug 42: Swift roundtable

Debug is a casual, conversational interview show featuring the best developers in the business about the amazing apps they make and why and how they make them. On this episode Natalia Berdys of Foodo Kitchen, Don Melton, former director of internet technology at Apple, and Brent Simmons of Vesper join Guy and Rene to talk about Swift, its future, Sprite Kit, and more!

Support Debug: Go to podsurvey.com/debug to take our survey and get a chance to win a $100 Amazon Gift Card. Go to lynda.com/debug to start your 7-day free trial. Go to getharvest.com and use offer code DEBUG by August 1st to receive 50% off your first month.

Show notes

Panel

Feedback

Question, comment, recommendation, or something you want us to follow up on for the next show?

Email us at debug@mobilenations.com or leave a comment below.

Have something to say about this story? Share your comments below! Need help with something else? Submit your question!

Rene Ritchie

Editor-in-Chief of iMore, co-host of Iterate, Debug, Review, Vector, and MacBreak Weekly podcasts. Cook, grappler, photon wrangler. Follow him on Twitter and Google+.

More Posts

 

6
loading...
16
loading...
74
loading...
0
loading...

← Previously

Environment the focus of Apple's presentation at education conference

Next up →

How to trim videos on your iPhone or iPad

Reader comments

Debug 42: Swift roundtable

11 Comments

Well done Rene. Good group you pulled together on this one. Great to hear more discussion on accessibility/inclusivity. Can you also include the Medium link for Swift articles?

The main objection the panel had to open sourcing Swift was that there would be "so many forks". This is baseless, and hearing the panel resort to ad hominems rather than discuss the point was disappointing.

First, if there were, why would that be a bad thing? Apple could (and no doubt would) ignore 99% of the activity. If that 1% could yield improvements from outside, e.g. Cydia developer hired for Notification Center, or even more recently the changes in Swift arrays, why on earth not?

Secondly, there would not be. As somebody (Guy?) points out not 3 minutes later, and completely unaware of the contradiction, there are virtually no forks of obj-c because Apple owns and does not open the runtime.

Since Swift requires the same runtime, there is no reason to believe a horde of "communists" would rush to fork a new language in ways they cannot use any more than they forked the old one. The only people who would bother would be those with a deep academic interest in language design - precisely those people who might contribute something of use.

Sent from the iMore App

Having programmed the Mac since 1988 (and Amiga before that), and as a cross-platform developer now, I really enjoy the tech talk, especially the historical stuff.

But you guys have to get over your hatred/fear of C++. In my industry, which is heavily performance-focused, templates and operator overloading are extremely useful and powerful. We're not ALL shooting ourselves in the feet, guys!