Earlier quoted context omitted.
They said it will happen by the end of 2015.
They said they would make facetime an open standard. Still waiting.
Here's a story about facetime: http://www.fiercedeveloper.com/story/facetime-open-standard-...
“Swift will be open source later this year”
241–250 of 573 posts
Re: “Swift will be open source later this year”
#242Earlier quoted context omitted.
Hey, look me up in a year and explain why you were wrong. Go has been out for 6 years and has less than 10,000 questions on StackOverFlow: http://stackoverflow.com/questions/tagged/go Swift has 37,000 questions in its first year: http://stackoverflow.com/questions/tagged/swift I'm a fan of Go. I built my websites in it and I've written a few small apps. However, you really are overlooking how much of a difference the…
OTOH There are 70k Go repos on GitHub vs 31k for Swift (vs ~5k for Rust) - https://github.com/search?l=go&q=stars%3A%3E-1&ref=searchres... - https://github.com/search?l=swift&q=stars%3A%3E-1&ref=search... - https://github.com/search?l=rust&q=stars%3A%3E-1&ref=searchr...
Swift repos will pass Go within 12 months. I think most iOS developers were holding off on Swift. Heck, Xcode and Swift, etc only became usable earlier this year.
Re: “Swift will be open source later this year”
#243I will love to see how Android apps will be written in Swift, not because its an Apple language, just because I didn't like Java at all (don't know the Oracle Java but the Java supported by Android lack of some features of an actual language).
Also the first challenge will be to build a library that implement all the Swift UI elements to Android (or vice versa) or better Google reinvent their UI or at least add more features and turns Android in a real MVC (bind the view with the controller).
Re: “Swift will be open source later this year”
#244I will love to see how Android apps will be written in Swift, not because its an Apple language, just because I didn't like Java at all (don't know the Oracle Java but the Java supported by Android lack of some features of an actual language). Also the first challenge will be to build a library that implement all the Swift UI elements to Android (or vice versa) or better Google reinvent their UI or at least add more…
Maybe Apple Music is!
Re: “Swift will be open source later this year”
#245For game devs, hopefully we can look forward to Swift support in Unity then. C# and Booscript are fine, but I'd welcome a language that puts the tool closer to iOS development.
Re: “Swift will be open source later this year”
#246Earlier quoted context omitted.
I'm not trying to be contrarian, but I fail to see what great type systems (or lack of them) have to do with YAGNI or writing poorly architected enterprise apps. Are you saying the main application of type systems is writing overengineered enterprise apps? Do you think type systems have no place in well-architected and/or minimalist apps? Can you elaborate more?
im saying those with a propensity to build such systems invariably choose strongly typed languages and in those languages that is the culture and the language encourages it. Eg.rewriting base classes to use IWritableStream instead of looking up the write method and calling it.
You seem to be confusing Java-like interfaces and design patterns with types. That's not representative of what great type systems can do for you.
Re: “Swift will be open source later this year”
#247I will surely be downvoted for speaking so off the cuff, but I haven't really enjoyed swift so far. How has the general developer reception been to the language, not just with respect to obj-c, but also to java or any other turing complete language?
I think it's terrible. Parsing a JSON response into a Swift object takes a full-day to figure out when it's literally just JSON.parse(response) in any other language. You can't pass immutable structures (structs) into NSNotifications and I can't figure out why. It's confusing and poorly documented, and a complete chore to use. React Native is a godsend.
How is React "native" again? I'm not sure I understand how something not written in Swift or Obj. C is 'native.' This is only 30% snark; I actually don't know the answer. React is from the same people that thought html5 was a good idea for a mobile application right? I am not bashing React; I am only curious how it's considered native. Does it have official support from the iOS APIs? Can you integrate Objective C libraries with React? I just don't get it.
I also don't get how a JSON parse takes half a day. If you know the language it shouldn't take that much time. If you don't know the language then a complaint wouldn't be intellectually honest would it?
Re: “Swift will be open source later this year”
#248I remember a thread on HN [1] from a few months ago talking about how apple was never going to do this. I'm so glad they were able to pull it off! Good for you, Apple! [1] https://news.ycombinator.com/item?id=8488808
Or Apple saw that and decide to change its mind. Sometimes companies change their minds this way, like how Microsoft changed its mind on the banning of DVDs for Xbox, even though they never "officially" said they would do that before the announcement of the Xbox One, but it was strongly "rumored" they would do that. I'm sure that's what they intended, but the outrage was too big to let it be.
Apple is never going to send me a free MacBook Pro and Thunderbolt display. Never.
Re: “Swift will be open source later this year”
#249Earlier quoted context omitted.
I wonder what this will mean for Qt and QML.
Why? Swift is a language and Qt is GUI framework
QML is akin to swift. Let's say, QML is to Qt as Swift is to Obj-C + native GUI libraries.
The purpose and syntax of QML and Swift are similar, too.
PS: Qt is not only a GUI framework. It's a cross platform C++ framework.
Re: “Swift will be open source later this year”
#250Earlier quoted context omitted.
ObjC is really just plain C, plus some Smalltalk-like semantics within the square brackets. This means you end up with all the "footguns" of C, plus dynamic OO behavior. Swift is like Rust in that it's intended to be fast, "safer", and compiles to LLVM bytecode. Also, Swift and Rust both use Option types for error reporting rather than exceptions or error codes. In the same sense that Rust is a way to leave behind ol…
I wouldn't say optionals are necessarily for error reporting. According to this slide[0], actually, we're going to be getting a proper error-handling model in Swift 2— we'll hear more either today or tomorrow. [0] http://www.apple.com/live/2015-june-event/eda6e3f7-0fda-4b46...
You can get an overview in the prerelease version of the Swift book - https://itunes.apple.com/us/book/swift-programming-language/...