4 ms·

Of course Apple continues to invest into Swift, making it better and writing more code in it. There's no doubt about that. This is an hour long talk. I don't s

Of course Apple continues to invest into Swift, making it better and writing more code in it. There's no doubt about that. This is an hour long talk. I don't see anything in the slides that indicates that Apple management has decreed that Swift is the sole successor language to C++, forsaking all others, and winding down their Rust codebases. Could you help me find out where that is in this talk?

pjmlp 3y ago
There are zero references to Rust on that talk. It is all about C, C++, Objective-C and how Apple is replacing them with Swift. Rust isn't even shown on languages in use at Apple, https://youtu.be/lgivCGdmFrw?t=284 https://youtu.be/lgivCGdmFrw?t=284 As for tracking down the exact minutes of each Swift reference, maybe I will try to find some time on my side to prove me right on the Internet.
- steveklabnik 3y ago
  What I am saying is that you aren't wrong, just that it comes across as a bit of a non-sequitur. The comment I was replying to says that Swift is the only language for the future. I am pushing back about that and that only. Of course they're not abandoning Swift. Of course they're moving away (in many cases) from C and C++. That doesn't imply that Swift is the only tool they will use, or that they're reversing course from the codebases they've already ported to Rust.
  - pjmlp 3y ago
    So I got some time to go through the video, - Overview of C, C++, Objective-C and Objective-C++ history on Apple platforms From https://youtu.be/lgivCGdmFrw?t=169 https://youtu.be/lgivCGdmFrw?t=169 to https://youtu.be/lgivCGdmFrw?t=306 https://youtu.be/lgivCGdmFrw?t=306 - How Swift fits into the picture https://youtu.be/lgivCGdmFrw?t=317 https://youtu.be/lgivCGdmFrw?t=317 Key statements. "Apple is very serious making Swift viable anywhere on this chart..." Meaning a chart showing "UI Apps, Portable utililities, Platform libraries, Portable libraries, Kernel and below." "...that is because we feel we need a successor language anywhere on this chart, so we are putting Swift at the kernel and below, as well as, platform libraries, and not just UI application, and we think it is a very important future for the language, we are very commited to it" Up to https://youtu.be/lgivCGdmFrw?t=352 https://youtu.be/lgivCGdmFrw?t=352 - Basic Expectations "We need to focus on adding one sucessor language" "Every language we add comes with extra complexity, in terms of tooling, XCode support, build system support and so on, as well as, language problems making them interoperate" "We have four precessor languages, we don't want four sucessor languages" "Should be accessible as first language, for people coming into our platform" From https://youtu.be/lgivCGdmFrw?t=360 https://youtu.be/lgivCGdmFrw?t=360 to https://youtu.be/lgivCGdmFrw?t=411 https://youtu.be/lgivCGdmFrw?t=411 "At the same time, if we want to make it usable in kernel, we need to provide enough control to make it usable in such environments" "In particular that means being able to scale down to a minimal runtime" From https://youtu.be/lgivCGdmFrw?t=420 https://youtu.be/lgivCGdmFrw?t=420 to https://youtu.be/lgivCGdmFrw?t=493 https://youtu.be/lgivCGdmFrw?t=493 - Problems with C https://youtu.be/lgivCGdmFrw?t=493 https://youtu.be/lgivCGdmFrw?t=493 - Overview of Swift "So we feel pretty strongly, obviously at Apple our sucessor language is Swift and I am here to talk about features of Swift, both to try to sell you on to it, but also to talk about the things we think are pretty necessary and the ways in which a programming language can support, you know, clear code, safer and more correct code." "Like I said before, Apple has always intended for Swift to be a sucessor language for all of our predecessors, from the top to the bottom of our stack, accessible to novices, powerful enough for experts, it is real a tall order. From https://youtu.be/lgivCGdmFrw?t=1996 https://youtu.be/lgivCGdmFrw?t=1996 to https://youtu.be/lgivCGdmFrw?t=2042 https://youtu.be/lgivCGdmFrw?t=2042 Quite clear that Swift is the future and zero mentions of Rust.

pjmlp 3y ago

There are zero references to Rust on that talk. It is all about C, C++, Objective-C and how Apple is replacing them with Swift. Rust isn't even shown on languages in use at Apple, https://youtu.be/lgivCGdmFrw?t=284 https://youtu.be/lgivCGdmFrw?t=284 As for tracking down the exact minutes of each Swift reference, maybe I will try to find some time on my side to prove me right on the Internet.

steveklabnik 3y ago
What I am saying is that you aren't wrong, just that it comes across as a bit of a non-sequitur. The comment I was replying to says that Swift is the only language for the future. I am pushing back about that and that only. Of course they're not abandoning Swift. Of course they're moving away (in many cases) from C and C++. That doesn't imply that Swift is the only tool they will use, or that they're reversing course from the codebases they've already ported to Rust.
- pjmlp 3y ago
  So I got some time to go through the video, - Overview of C, C++, Objective-C and Objective-C++ history on Apple platforms From https://youtu.be/lgivCGdmFrw?t=169 https://youtu.be/lgivCGdmFrw?t=169 to https://youtu.be/lgivCGdmFrw?t=306 https://youtu.be/lgivCGdmFrw?t=306 - How Swift fits into the picture https://youtu.be/lgivCGdmFrw?t=317 https://youtu.be/lgivCGdmFrw?t=317 Key statements. "Apple is very serious making Swift viable anywhere on this chart..." Meaning a chart showing "UI Apps, Portable utililities, Platform libraries, Portable libraries, Kernel and below." "...that is because we feel we need a successor language anywhere on this chart, so we are putting Swift at the kernel and below, as well as, platform libraries, and not just UI application, and we think it is a very important future for the language, we are very commited to it" Up to https://youtu.be/lgivCGdmFrw?t=352 https://youtu.be/lgivCGdmFrw?t=352 - Basic Expectations "We need to focus on adding one sucessor language" "Every language we add comes with extra complexity, in terms of tooling, XCode support, build system support and so on, as well as, language problems making them interoperate" "We have four precessor languages, we don't want four sucessor languages" "Should be accessible as first language, for people coming into our platform" From https://youtu.be/lgivCGdmFrw?t=360 https://youtu.be/lgivCGdmFrw?t=360 to https://youtu.be/lgivCGdmFrw?t=411 https://youtu.be/lgivCGdmFrw?t=411 "At the same time, if we want to make it usable in kernel, we need to provide enough control to make it usable in such environments" "In particular that means being able to scale down to a minimal runtime" From https://youtu.be/lgivCGdmFrw?t=420 https://youtu.be/lgivCGdmFrw?t=420 to https://youtu.be/lgivCGdmFrw?t=493 https://youtu.be/lgivCGdmFrw?t=493 - Problems with C https://youtu.be/lgivCGdmFrw?t=493 https://youtu.be/lgivCGdmFrw?t=493 - Overview of Swift "So we feel pretty strongly, obviously at Apple our sucessor language is Swift and I am here to talk about features of Swift, both to try to sell you on to it, but also to talk about the things we think are pretty necessary and the ways in which a programming language can support, you know, clear code, safer and more correct code." "Like I said before, Apple has always intended for Swift to be a sucessor language for all of our predecessors, from the top to the bottom of our stack, accessible to novices, powerful enough for experts, it is real a tall order. From https://youtu.be/lgivCGdmFrw?t=1996 https://youtu.be/lgivCGdmFrw?t=1996 to https://youtu.be/lgivCGdmFrw?t=2042 https://youtu.be/lgivCGdmFrw?t=2042 Quite clear that Swift is the future and zero mentions of Rust.