Live data from Hacker News

Welcome Chris Lattner

tesla.com

191–200 of 291 posts

Re: Welcome Chris Lattner

#191

Earlier quoted context omitted.

ARC is a whole debate, but the one thing it is not is simple and I would argue its more error prone than a traditional GC. I've used it for most of my career and I have seen what sloppy/unaware coding can do to it. Lattner is a well known expert on compilers. Having used Swift since its inception, I would call into question the reliability of the Swift LLVM compiler. In its current state (3.0.2) its absolutely terrib…

ARC is a tradeoff between manual and automatic memory management. Requring a little bit more care from programmer is intentional, not a disadvantage as you picture it, it is a price for not having, you know, GC. GC is less error prone not for free but at the price of eating CPU and memory, which in the world of mobile devices equal less battery life, so it is quite desirable for iPhones and MacBooks software not to h…

ARC is automatic memory management.

"The Garbage Collection Handbook", chapter 5

http://gchandbook.org/

Re: Welcome Chris Lattner

#192

Earlier quoted context omitted.

The right comparison for ARC is with manual memory management -- not GC.

Depends on what your point is. Both ARC and GC are approaches to limit the complexity and difficulty of memory management. As such, I think it's very reasonable to compare them, because they're different approaches to the same underlying problem. FWIW, as someone who was a Java programmer for over a decade before learning Objective C right after ARC came on the scene, I greatly prefer ARC over garbage collection. I f…

ARC is a GC implementation algorithm, you probably mean tracing GC algorithm.

"The Garbage Collection Handbook", chapter 5

http://gchandbook.org/

Re: Welcome Chris Lattner

#193

Earlier quoted context omitted.

The right comparison for ARC is with manual memory management -- not GC.

Not really. They are both valid comparisons, since ARC is much easier to work with than manual management and can offer more predictable performance than GC. That said, it's also slower than manual management and can be trickier to work with than GC.

ARC is a GC implementation algorithm, you probably mean tracing GC algorithm.

"The Garbage Collection Handbook", chapter 5

http://gchandbook.org/

Re: Welcome Chris Lattner

#194

Earlier quoted context omitted.

Do you use Swift at all? -edit- I meant it as a serious question. But the person who responded to me sums up the issues.

This is downvoted presumably for lack of information, but it's pretty much true. The Swift compiler segfaults very frequently. I do find this amusing in that it's the compiler for a theoretically largely-memory-safe language (yes the compiler is written in C++, it's still funny). The syntax highlighter in Xcode, which is driven by the same stuff, also crashes, which breaks autocompletion and even indentation . Using…

The most annoying one is the incremental compiler is broken under Xcode 8, leading to full recompiles every time a line of code is modified.

https://forums.developer.apple.com/thread/62737?start=0&tsta...

Re: Welcome Chris Lattner

#195
post #191

Earlier quoted context omitted.

ARC is a tradeoff between manual and automatic memory management. Requring a little bit more care from programmer is intentional, not a disadvantage as you picture it, it is a price for not having, you know, GC. GC is less error prone not for free but at the price of eating CPU and memory, which in the world of mobile devices equal less battery life, so it is quite desirable for iPhones and MacBooks software not to h…

ARC is automatic memory management. "The Garbage Collection Handbook", chapter 5 http://gchandbook.org/

Yup but people love to argue over the small shit. Chris Lattner even refers to ARC as a form of GC.

Re: Welcome Chris Lattner

#196
post #52
post #32

Elon Musk is the new Steve Jobs. He is an inspirational leader and talented people want to work with him. It appears it will be harder and harder to attract and keep talent at Apple with out a leader like Steve Jobs.

I see Musk as more of a Bushnell/Woz hybrid. He knows his shit technically, which is why good people want to work with him. Jobs knew how to delegate knowing his technical shit to others though.

A lot of his best insights required technical knowledge - adopting Ethernet, SCSI, Mach kernels, BSD userland, object oriented programming, Postscript, TrueType fonts, WebObjects (and Java server, while ditching it on the client), html5 (over Flash)

Re: Welcome Chris Lattner

#197

Apple has a car project. Autopilot must be one of its core features. But Apple would not create a VP-level position for Autopilot or any one feature for any of their products (even if they it called something else for secrecy/generalization reasons). This move increases his compensation and clout. Post-Tesla, he'll only have VP or founder titles elsewhere, never anything lower-level (unless he gets his old job back).…

>That Apple could not retain him speaks volumes of the company they've become.

Sorry if this sounds naive (and it's not intended as veiled criticism), but could it not be the case just that he is more valuable to Tesla so they are able to justify offering him more compensation?

Re: Welcome Chris Lattner

#198
post #187

Earlier quoted context omitted.

If I remember right, its just the calculator app. Lol....

The dock and launchd were rewritten in Swift for Sierra. There is a WWDC session talking about it.

Well that doesn't bode well ;) Sierra's dock is sooo buggy. I have to restart my machine numerous times a day because the dock stops working, literally doesn't work lol. I'm sure theres a way to restart just the dock app, but eh i've been quite busy. Sierra has been one of the buggiest version of Mac I can remember using.

I would surprised if they actually did tho. I know someone did some static analysis of the apps for mac and iOS and found Swift was barely used at all.

Re: Welcome Chris Lattner

#199
post #196
post #52

Earlier quoted context omitted.

I see Musk as more of a Bushnell/Woz hybrid. He knows his shit technically, which is why good people want to work with him. Jobs knew how to delegate knowing his technical shit to others though.

A lot of his best insights required technical knowledge - adopting Ethernet, SCSI, Mach kernels, BSD userland, object oriented programming, Postscript, TrueType fonts, WebObjects (and Java server, while ditching it on the client), html5 (over Flash)

Were they his personally formed insights or did they come from talking to the right people?
Post reply on HN