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.
"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"
"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"
"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.
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
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.