Yeah, but the funny thing is how Apple's AOT compilation toolchain was being discussed by some Apple fans as the way to go.

Now they turn around and follow what the others are doing.

It still is AOT. There's just an intermediary step, which is what you send to Apple, but the code is compiled in its servers, not in the runtime.

It's not like LLVM doesn't have several steps already in its pipelines.

I guess you don't know how MDIL and .NET Native work.

Not sure where you're getting at.

Like Apple's .NET Native is AOT.

Like Apple's .NET Native compiles to native code in the server.

It's your comment that gave the impression that you thought Apple's new bitcode thing is not AOT and that they follow MS in this not-AOT-ness.

It might not have been what you meant, but it's not very clear from the phrasing:

>"(...) Apple's AOT compilation toolchain was being discussed by some Apple fans as the way to go. Now they turn around and follow what the others are doing"

This reads like Apple had an AOT compilation toolchain that Apple fans thought it was "the way to go" and now Apple dones't have one (AOT compilation toolchain) anymore following MS lead in this regard.

Whereas what you actually meant was probably that Apple fans thought that Apple's PREVIOUS AOT compilation toolchain was the way to go, but now they've changed course and went for an MS style AOT compilation toolchain.

(it read like you think "Apple's AOT toolchain" was a thing of the past, and not they follow MS which doesn't have AOT).

> Whereas what you actually meant was probably that Apple fans thought that Apple's PREVIOUS AOT compilation toolchain was the way to go, but now they've changed course and went for an MS style AOT compilation toolchain.

Exactly.

Yeah, took me a while to get it can mean that, I think the straightfoward reading is the other one.

Well, not native speaker here. :)

Both .NET Native and this (bitcode) are an AOT compilation toolchain.

Who says otherwise?

What I said is that I heard from many Apple fans that it didn't make sense the MDIL/.NET Native compilation model[0] and directly compilation from XCode to the device was the way to go.

[0]Uploading IL to the store and having a server based compiler generate native code before download.