Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Blog Pricing

Chris Lattner

๐Ÿ‘ค Speaker
See mentions of this person in podcasts
2524 total appearances

Appearances Over Time

Podcast Appearances

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

Right.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so I think that the tryouts are very different if you're building a, you know, large scale production system versus you're building and exploring a notebook.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

Well, and that is the sign.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

I love you, man.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

But that is a sign of somebody who likes control.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so, yes, I think that you'll like FN.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

I think you'll like Mojo.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

So, I mean, we use the same, we're the same as Python, right?

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

But we implement in a very different way, right?

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so if you look at other languages, like we'll pick on C++, our favorite, right?

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

C++ has a thing called zero cost exception handling.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

Okay.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And this is, in my opinion, something to learn lessons from.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

It's a nice, polite way of saying it.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

If you don't throw an exception, there's supposed to be no overhead for the non-error code.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so it takes the error path out of the common path.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

It does this by making throwing an error extremely expensive.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so if you actually throw an error with a C++ compiler using exceptions, it has to go look up in tables on the side and do all this stuff.

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

And so throwing an error could be like 10,000 times more expensive than returning from a function, right?

Lex Fridman Podcast
#381 โ€“ Chris Lattner: Future of Programming and AI

Yeah.