How he had time to work a director-level job at , develop a new programming language, oversee/participate in the OSS work for LLVM/Clang/Swift, and build things like these I'll never know.
My VP is a world class ping-pong player, does just as much, etc.
You delegate things well enough and build good enough teams that you don't have to worry about this.
IE he did none of the things you mention alone, he built teams that were effective at doing those things.
When folks point out he isn't still the lead author of llvm or clang and hasn't been for a long time (at least on those projects, he hasn't written a patch in a while), people see it as slighting Chris. But it's not. The way you have time to do the stuff you are talking about is by building up communities, teams, and infrastructures so you don't have to be contributing to them all the time.
Nobody really scales by being infinitely faster/better, they scale by building up people.
"The computer industry has a lot of remarkable people in it, but they’re low-dimensional. Alan Kay is very high dimensional: a big space of instincts and interests and capabilities. I mean, the guy could design furniture. He planned a whole programming language while he was building a harpsichord. He was able to do the two things concurrently."
But he does mention the house took months to build, and handcrafts are a great hobby...
Wait, what? This is the first I've heard of Apple forbidding you from talking to anyone else. Unless you mean specifically about the project, and not just ever and about anything?
Weren't all these things part of his job at Apple? Things he could reasonably do during working hours? If so the question is how did he have a job + spare time which is easier to answer.
Massive respect for Lattner and his long, multi-year, persistence to making amazing world-changing software and actually caring about open source.
One of the best ATP episodes in years!
Now I wish there was a podcast where language implementors could talk about all of this stuff.
I just don't get the yellow car bit at all.
Is this a typo? As a programmer, I wish I was as technical as Chris Lattner's used kleenex.
- Chris is leaving because Apple is doomed
- Chris couldn't get into the rumored Apple car division
- Chris was being forced into a more VP/management role
Note that it was actually a "white car" bit. Casey, Marco and John originally did a podcast called Neutral which was about cars, and the very first line of the first episode was Marco quizzing Casey on why he only seemed to buy white cars. White cars have become synonymous with Casey ever since, and Marco took the opportunity to bring it up again with Chris.
(Technically, the question was "what is it that makes somebody buy a white car?")
Some color/vehicle combinations are classics.
Pull me over red however, is more what I'd consider in the classic category.
Was ever there any question or doubt about Lattner's technical ability?
I have my misgivings with the iOS/macOS development stack (chief among them being Xcode), but Swift is probably the language I enjoy writing in most. It's powerful and expressive and pleasant.
I'm happy to know that even with Chris leaving, the pieces are set in motion for the language's expansion to other contexts.
Clang is pretty amazing. The world before and after Clang are very different places, so I'd say Apple has had a really positive impact here.
It seems like he believes pervasive borrow checking is not the right approach for the average application developer, even if it is the right approach for systems programming. He also mentioned eventually having a mode that only uses borrow-checking without ARC, e.g. for writing firmware.
Rust originally had lofty goals to support compile-time lifetime proving and GC mode; GC was abandoned for sensible reasons. Swift uses ARC, so it is trying to support full-ARC, mixed mode, and compile-time lifetime. Whether that is achievable remains to be seen.
I was just trying to say that its design forces discussion of the ownership model to be very early on in the description of the language. It is typically in the first page/chapter of the tutorials I've seen.
This approach doesn't align well with Swift's approach of progressive disclosure of complexity.
Then use Swift. Other than the approach to memory, Swift is extremely similar to Rust.
> I wish swift scene on linux becomes viable in the next version.
Swift 3.0 is totally viable on Linux. And Swift package manager works great, although it's not quite as nice as Cargo (yet!). I've been very impressed with Swift on Linux, but I've yet to use it for production (although there are lots of folks who are). There are some very nice web frameworks for Linux in Swift. I'd say that for web, Swift on Linux is more advanced than Rust. Take a look at Perfect, Zewo, Kitura, etc. They've even got lots of authentication/authorization plugins, which last I checked no Rust framework had.
Here's an overview of how theoretical language features could enable library implementations of coroutines+channels, async/await, or actors:
Which bit are you interested in? If it's a <~10 minute section, I'll transcribe it for you over the weekend. Contact details are in my bio.
Edit: duh, Patient0 notes it below and it's one of the chapters of the podcast! Drop me an email so I have your address; I'll also post it online somewhere and drop a link here.