Chris Lattner on the Realm WWDC 2017 Swift Panel
Could someone explain why I should build a language developed entirely  by and for writing Apple ecosystem products? It seems like if I&#x27;m not targeting MacOS or iOS directly, the long list of benefits suddenly looks much, much smaller compared to e.g. JVM, .NET, Go, etc etc.<p>&quot;letʼs start hacking, letʼs start building something, letʼs see where it goes pulling on the string&quot; feels scarily accurate, and it&#x27;s unclear where the language will be in 5 years.<p>Among other things, there&#x27;s no way to disable objective-c interop, even though it complicates the language and feels like someone merged smalltalk, C++, and ML—not a pretty combination. But—literally the only reason you&#x27;d enable that would be to work with Cocoa&#x2F;UIKit.<p>I&#x27;m still out on ARC—it was much less of a problem than I expected on my last project, but it never feels like an optimal solution, and you can never just &quot;forget about it for the first draft&quot; the way you can a VM&#x27;s GC.