Can anyone tell me about the interop situation? I'm working on my first iOS app and doing it all the old way with Obj-C, and some things have been a little difficult to grok even though they've been around a while(AVFoundation). I'm very interested in the new Metal graphics API that Apple showed at their presentation. Not sure if I should just switch to Swift for everything now or continue learning/working in Obj-C and slowly transition.
Swift Has Reached 1.0
151–160 of 180 posts
Re: Swift Has Reached 1.0
#152So, what kind of 1.0 release is this? - It's Keynote time/September 9, so we call what we have, crashing bugs included, 1.0. - We culled the features that do not work reliably yet, polished the good parts, and called it 1.0. - This is a/the set of features that we consider to form a good product, and all features work reasonably well.
I'd say it's a bit of all three. This is clearly a marketing-driven 1.0. It's really not ready, and wouldn't reasonably be called a 1.0 otherwise. However, they've been pretty good about sticking to a solid set of features and not over-extending themselves for this initial release. It seems fairly clear that they intend to go in and fill out a lot of stuff later, and preferred a smaller set of solid features to start…
They've also been pretty clear that the language is going to be in a state of flux for long while. From the Swift Blog:
"Binary Compatibility and Frameworks
While your app’s runtime compatibility is ensured, the Swift language itself will continue to evolve, and the binary interface will also change. To be safe, all components of your app should be built with the same version of Xcode and the Swift compiler to ensure that they work together.
This means that frameworks need to be managed carefully. For instance, if your project uses frameworks to share code with an embedded extension, you will want to build the frameworks, app, and extensions together. It would be dangerous to rely upon binary frameworks that use Swift — especially from third parties. As Swift changes, those frameworks will be incompatible with the rest of your app. When the binary interface stabilizes in a year or two, the Swift runtime will become part of the host OS and this limitation will no longer exist."
Re: Swift Has Reached 1.0
#153Earlier quoted context omitted.
C# is in front of all three in mobile space (it compiles to native of course). C# is the only language that is both modern and spans all major mobile platforms. http://en.wikipedia.org/wiki/Xamarin
Considering the minuscule market share that Windows Mobile currently has, C# is close to nonexistent on mobile as of today.
Unity3d alone completely invalidates this claim.
Re: Swift Has Reached 1.0
#154Re: Swift Has Reached 1.0
#155Earlier quoted context omitted.
Any other company who's language runs over 1.3 million apps used by hundreds of millions of people on average every 6 minutes?
Oracle and Microsoft. But their languages (Java and C#) are not platform dependent. Just an example: >Microsoft released C# Roslyn source code, announce Linux support with K Runtime this year They're going to the right direction, maybe someday... >Apple released Swift, closed source language that runs only on one platform (Mac) Apple is so awesome, keep innovating guys! Now let's write a webstack and nosql db using S…
C# is hideous to get running consistently (if at all) with recent versions and libraries cross platform. Perhaps this will change in the future, but they've not been particularly brilliant about it over the past decade
Re: Swift Has Reached 1.0
#156Earlier quoted context omitted.
Unity3d alone completely invalidates this claim.
Are there many apps written in Unity? Or is it only games?
Mostly games which are a kind of apps. And games are the most popular apps, e.g.: http://www.statista.com/statistics/270291/popular-categories....
Re: Swift Has Reached 1.0
#157Hey guys, do you know if swift will be ever open-sourced? After the WWDC they said that was early to think about it while in beta. So, what's the status now?
What is the practical difference if it's open-source or not? It'll still be OSX-native code, and every OSX user has access to it for free anyway. Or would that enable a Linux port?
If Apple decides/realizes Swift was a bad idea, you will be out of luck with your codebase. Unlike open source where users can continue the work of the corporation.
Re: Swift Has Reached 1.0
#158Earlier quoted context omitted.
Their live feed yesterday was only available on Safari. Isn't it obvious that they want their herd only inside of a barn?
> they want their herd only inside of a barn? Awesome. Who should I switch to that doesn't want that?
Apple is the most extreme example. I was able to watch Microsoft's live streams in Chrome for example.
Re: Swift Has Reached 1.0
#159Earlier quoted context omitted.
Oracle and Microsoft. But their languages (Java and C#) are not platform dependent. Just an example: >Microsoft released C# Roslyn source code, announce Linux support with K Runtime this year They're going to the right direction, maybe someday... >Apple released Swift, closed source language that runs only on one platform (Mac) Apple is so awesome, keep innovating guys! Now let's write a webstack and nosql db using S…
C# is hideous to get running consistently (if at all) with recent versions and libraries cross platform. Perhaps this will change in the future, but they've not been particularly brilliant about it over the past decade
I don't know what libraries you talking about but nearly everything from nuget starting with image processing and ending with orms and crypto work just fine on linux.
Even more when K will come out I don't think there will be any worries at all.
Re: Swift Has Reached 1.0
#160Can anyone tell me about the interop situation? I'm working on my first iOS app and doing it all the old way with Obj-C, and some things have been a little difficult to grok even though they've been around a while(AVFoundation). I'm very interested in the new Metal graphics API that Apple showed at their presentation. Not sure if I should just switch to Swift for everything now or continue learning/working in Obj-C a…
I wouldn't recommend Swift to anyone that's new to the iOS SDK. I answered this question recently on stack overflow (http://stackoverflow.com/a/25751738/77567). Here's what I said:
- Objective-C will be around and supported for a long time. (Apple has a massive amount of Objective-C source code that it's not going to port to Swift any time soon.)
- Almost all iOS tutorials, examples, and books use Objective-C.
- Almost all iOS-specific third-party source code you might want to use is implemented in Objective-C.
- It's easier to use C and C++ libraries from Objective-C than from Swift.
- There are many Objective-C experts you can get help from. There are very few Swift experts.
- The Swift language and its standard library are currently not very well documented.
Stick with Objective-C for now. When you're comfortable with the iOS SDK and Swift is better documented, you can consider learning Swift.