871–880 of 970 posts
Earlier quoted context omitted.
Are you sure it wasn't just because you were then no longer doing a large memcpy repeatedly?
Yes it was entirely covered by that :) I think it was covered by "naive memory management" and "shitty outsourcing". I'm paid to fix their stuff.
Book Link: https://itunes.apple.com/us/book/the-swift-programming-langu...
Swift is a new programming language for creating iOS and OS X apps.
Swift builds on the best of C and Objective-C, without the constraints of C compatibility. Swift adopts safe programming patterns and adds modern features to make programming easier, more flexible, and more fun. Swift’s clean slate, backed by the mature and much-loved Cocoa and Cocoa Touch frameworks, is an opportunity to reimagine how software development works.
This book provides:
- A tour of the language.
- A detailed guide delving into each language feature.
- A formal reference for the language.
Hope it helps.
Me (running arch linux): Oooh! I'd love to learn a new language. And great, they have a free ebook it looks like to describe it! Apple: To download Apple Inc.’s 'The Swift Programming Language', you need to have iTunes. Me: What? Apple: Using a 64-bit edition of Windows? On a Mac? Me: No. That experience just killed a potential programmer for you right there, Apple. I had a few hours to kill, and was pumped to jump o…
Earlier quoted context omitted.
Hard to say, as yet. I'd expect it to be pretty open in the end, though; they're using LLVM and the Objective C runtime, both of which are open and usable on other platforms. I guess we'll see if they release the compiler.
Object C was created through changing the GCC and hence had to be released as open source due to the licensing of GCC (I believe) [1]. Swift is an apple invention and I would predict that they have no intention of releasing source code of it for availability on other platforms. Apple is a very closed ecosystem. [1] http://en.wikipedia.org/wiki/Objective-C#Popularization_thro...
However, GCC is not longer used by the Apple toolchain. They could easily close up their work on Clang and LLVM, and haven't. Further, they're obviously still contributing - they've recently added their ARM64 backend to LLVM.
The Apple software ecosystem isn't particularly closed. Much list iOS and OS X, they're based on a pretty open foundation, with proprietary libraries on top.
I'm impressed that it looks like they're turning Bret Victor's demo into a reality with playground. Check out his demo if you haven't: https://www.youtube.com/watch?v=PUv66718DII Really, really interested and excited about learning Swift.
I find it a bit sad that with all of the languages that already exist, Apple found it necessary to invent a completely new one -- and then make it proprietary. Why not use Ruby, or Python, or JavaScript -- or even Go, Rust, Clojure, or Scala? (Yes, I realize that the latter two run on the JVM, which would have been problematic in other ways.) Heck, they could have bought RubyMotion and made Ruby the high-level langua…
I would've voted for buying/licensing Xamarin instead; C#/F# would've given them everything including a lot of fresh programmers. On the other hand i'm happy they didn't as they would've tossed out Android and (at least for me) there is no alternative yet to the speed / power of development here.
Earlier quoted context omitted.
While half of the things you checked in that copy-paste are wrong, let me take the bait and say why it will work: - it's not just an arbitrary language, it's the new officially sanctioned programming interface for Apple's gigantic, wildly profitable ecosystem - it's much more concise than Objective-C - it's faster than Objective-C - it's safer than Objective-C - it has more features than Objective-C - ...yet it's ful…
How is Swift safer than Obj-C? I'm not sarcastic or anything by the way, I just don't understand yet the foundation behind that statement.
Anyone else see quite a lot of Scala here?