Except that his phonetic sequence probably wasn't entirely correct. We don't repeat what we hear, we repeat what we think we hear, after we put our native tongue's filter over it to try to make sense of it. So what he said to Google voice probably wasn't completely accurate, but it still knew what he was talking about.
I don't know much about how Safari is for developers, but in my experience it is currently the best browser for the mac. The general performance of the browser (don't know about js benchmarks) and energy usage are a lot better. Also js based drag and drop is remarkably responsive, a lot more so than Chrome and Firefox. It does have a weird thing where it doesn't load Google sites for me sometimes.
Refering to Safari as "the new IE" isn't a comment about whether it's a good browser or not. It's because Safari is lagging some way behind the rest of the browsers when it comes to implementing new features based on standards. The problem is best illustrated by CanIUse.com ... http://caniuse.com/#compare=firefox+40,chrome+44,safari+8 ... Scroll to the bottom and look at the "Mixed support" table. Lots of green in the Chrome and Firefox columns, while there's lots of red in the Safari column.
Why this is a problem is that it means the web will stagnate. People will do new things, but only within the limits of the old technology. Many of the things Safari lacks are trivial to work around (an input color picker for example .. it's easy to do that in JS). Other things are much more important - picture elements and HTTP/2 being good examples.
Swift was developed in secret and launched to unsuspecting public in near 'complete' status in 2014 then a 1.2 version quickly followed. Now it is version 2.0 after one year of launch. That is some serious version inflation.
Kotlin was developed in the open from much of its development and you can see how the language evolves based on the feedback of early adopters. There is no rush to 1.0 until they feel they got the right mix of features.
I just think the way Jetbrains approached the development of the language is more responsible and it bodes well for future iteration of the language.
I just started learning Swift, and I keep running into stackoverflow answers saying "Here's how it worked in 1.0. In 1.2 you have to do this instead. But in 2.0 you do it this other way."
I would imagine based on the context of the sentence, that as JetBrains are taking their time with the language, they aren't rushing through developing it further and making mistakes etc.
For me, the swift language is becoming dangerously like Scala. It's becoming a really large language syntax-wise. Trying to incorporate too many features.
For my language, I'll do some proper advertising on it once I figure out version two; v1 is very much a testbed for playing around with language design.
As I said, in Haskell "unquantified type variables are implicitly universally quantified" i.e. type variables (which are always lowercase in Haskell, to distinguish them from concrete types which are uppercase) are always generic.
So it's true that in the Swift examples, you would need a convention to distinguish type variables from concrete types, or else you need to explicitly mark them as generic.
