Earlier quoted context omitted.
ARC is a GC implementation algorithm, you probably mean tracing GC algorithm. "The Garbage Collection Handbook", chapter 5 http://gchandbook.org/
I think it is time for you to buy more books.
Welcome Chris Lattner
241–250 of 291 posts
Re: Welcome Chris Lattner
#242Earlier quoted context omitted.
There are some web frameworks that are indevelopment. That does not mean Swift has gained any traction. Also having toyed around with one, the experience was not great. When writing a server, I would take Go over Swift anyday. It out preforms it, uses less memory, its simpiler, oh and it uses a "tradiontal" GC.
>uses less memory That is very much _not_ the case according to the testing I have done recently. Swift uses a lot less memory than Go unless the program uses only trivial amounts of memory in the first place. Using interfaces in Go data structures makes the difference even more pronounced. On top of that, all runtimes that use a tracing GC require tons of spare memory at all times unless programs are very carefully…
Re: Welcome Chris Lattner
#243Earlier quoted context omitted.
>uses less memory That is very much _not_ the case according to the testing I have done recently. Swift uses a lot less memory than Go unless the program uses only trivial amounts of memory in the first place. Using interfaces in Go data structures makes the difference even more pronounced. On top of that, all runtimes that use a tracing GC require tons of spare memory at all times unless programs are very carefully…
It will be great if you have any benchmark to share. From what s available on internet Swift does seem to use more memory than Go.
My own code is unfortunately a bit messy and entangled with unrelated stuff. If I find the time I'm going to clean it up.
Re: Welcome Chris Lattner
#244Earlier quoted context omitted.
> Wow, that was unexpected. Great poach by Tesla. Tangential, but I really hate the term "poach" when referring to recruiting employees. We shouldn't think of hiring people as "poaching", because employees are not property. You can't "poach" an employee because there's no ownership, and employees should be free to make their own decisions regarding their employment opportunities.
I'm not sure why OP was down-voted, you may disagree but his post was credible and merits a response.
Re: Welcome Chris Lattner
#245What's really interesting about this is not just that Lattner is brilliant and liked, but that is highlights just how critical software correctness and reliability is to autonomous vehicles. Naively one might have expected some machine learning expert to take over the reins at Tesla. But fast-moving Silicon Valley needs a fundamental shift in quality standards when it comes to safety-critical software, and if you loo…
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…
Re: Welcome Chris Lattner
#246Earlier 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…
Just to point out that the Swift LLVM compiler is written in C++. So it being unreliable doesn't necessarily say much about the reliability or goals of Swift as a language.
C++14 is a whole other world, and can be written with most (if not all) the safety guarantees you would expect from Swift or Rust.
I had to use it for a project and was very surprised about this too...
Re: Welcome Chris Lattner
#247Earlier quoted context omitted.
Exactly, Apple is to microcomputing what Tesla is to green power and vehicles. We'll see in 10 years after Musk is fired from Tesla by John Sculley.
> We'll see in 10 years after Musk is fired from Tesla by John Sculley. I know you are being facetious, but similar to Jobs, Musk got ousted as CEO from his first and second companies: Zip2 [1] and PayPal [2]. [1] Vance, Ashley (2015). Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future, p72. [2] https://en.wikipedia.org/wiki/Elon_Musk#X.com_and_PayPal
Re: Welcome Chris Lattner
#248Earlier quoted context omitted.
Just to point out that the Swift LLVM compiler is written in C++. So it being unreliable doesn't necessarily say much about the reliability or goals of Swift as a language.
It looks like you haven't used C++ in a while. C++14 is a whole other world, and can be written with most (if not all) the safety guarantees you would expect from Swift or Rust. I had to use it for a project and was very surprised about this too...
Re: Welcome Chris Lattner
#249Earlier quoted context omitted.
I find Swift to be getting worse each year. While sure i'm blessed that I don't have to write applications in assemble, I have grown jaded towards Swift. If it wasn't because I am an iOS developer, I would happily not use the language. I have been slowly positioning myself away from doing iOS development. I feel like a massive corporation like Apple can provide better tools to write apps for their walled garden than…
What would you recommend instead? C#? C++? C++ has become incredibly great recently after languishing in the C++2003 period for too long.
Re: Welcome Chris Lattner
#250Earlier quoted context omitted.
Pretty much none of Apple's current software is written in Swift though, from what I can tell.
Actually a fair bit is in Sierra. Apple decided apparently not to invest resources in targeting 32-bit platform support, so they have had to hold off shipping software relying on it until the platforms drop 32-bit support. Sierra did that last year, and I'd put $5 on iOS 11 doing that as well.
Apple can't write Swift libraries (at least not ones that are publicly exposed) until the ABI stabilizes, so that will not happen until at least Swift 4. Apple can write Swift apps as long as they don't need to support 32-bit Mac, which they haven't needed to do for years.