91–100 of 203 posts
It's amazing that Apple managed to go from hatching the idea in mid-2010 to releasing a fully working framework 4 years later, with tight IDE integration, huge amount of testing and compatibility without a single leak (that I've heard of).
It looks like Rust was a major influence. It has been interesting seeing all these posts claiming Swift borrowed from _their_ language. Obviously there is a lot of feature influence between languages but it was interesting to see the ones he called out explicitly.
It's a bit of a Rorschach test, sometimes. People see what's familiar to them.
I like Chris and what he has done, but... >>The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas... Seriously? What is a "documentation guru"? What is a "compiler optimization ninja"? I find language like this so distracting and asinine that I had to stop reading. Am I the only one?
It is quite possible that e was referring to people who he believed had taught him interesting aspects about the spirit of documentation or the philosophical way to view compiler optimisation. In which case the word would be apt.
He does not have a beard. I'm very skeptic this language will be successful
Earlier quoted context omitted.
It's not clear how much code is actually written in Swift so far, so I'm not sure how much testing/compatibility was required.
Not that it's particularly complicated, but they mentioned yesterday that the updated version of the WWDC app (which they released right after the keynote) is written in Swift. I don't know if that means "entirely written" or some parts, but they at least called attention to it.
Chris demonstrated Swift and Playgrounds at WWDC 2014: "I can build anything with Swift... from a social media application, all the way up to a high-performance, 3D game using Metal." https://www.youtube.com/watch?v=nKMAV6owYh4#t=6436 He wrote this chapter (entitled LLVM ) in the book, "The Architecture of Open Source Applications": http://aosabook.org/en/llvm.html * * * On the general topic, I wrote this [1] a littl…
Earlier quoted context omitted.
Not that it's particularly complicated, but they mentioned yesterday that the updated version of the WWDC app (which they released right after the keynote) is written in Swift. I don't know if that means "entirely written" or some parts, but they at least called attention to it.
Which implicitly means that swift code can be compiled for iOS 7. Which isn't surprising since the compiled code uses the ObjC runtime.
Earlier quoted context omitted.
Not trying to be rude, but if you've tried and actually FAILED to learn Objective-C multiple times, then you will have a much bigger problem with actually learning the Cocoa framework yourself. Objective-C does have a non-standard syntax, but its barrier of entry for actual learning is purely psychological and not technical.
Maybe the mistake could lie in starting with Objective C without first learning C? I'm thinking that a reasonably solid C foundation helps a lot in understanding why and how Obj-C works.
Earlier quoted context omitted.
Yes, you are the only one. Replace "guru" with "expert" and "ninja" with "expert" and continue reading. There are already no real ninjas in the world and soon there will be no real gurus. No one thinks twice when someone is called a marketing wiz (there are no real wizards any more). Language changes and metaphors using archaic terms are commonly introduced.
That's funny, because when such language is used in job postings, they are overwhelmingly frowned upon by HN folks. But I guess it's OK when someone like Chris does it... edit: judging by the downvotes, he seems to have a lot of fans. :)
(Yes, I know. I could use some downvotes.)
Earlier quoted context omitted.
"Underneath" just means "the level below where I'm writing". This has pretty much always been true, the way systems are layered. You write install scripts? Apps? Libraries? rendering engines? Drivers? OS? Firmware? Chip layout? You probably don't really know what goes on 'underneath' your layer.
I agree but I feel like with swift it's kinda reaching an extent and it really doesn't push you toward learning any other layer. Swift + playground feels like the new dreamweaver to me. Either people are gonna write ugly code that shows them what they want to do or keep building quality apps, I don't know, I guess future will tell us. But I guess my main point was just that where I personally would try to reduce the…