4 ms·
Well, as long as we can agree that shitty bytecode interpreters are not the way to go ;) I think AOT/JIT as a dichotomy is stupid, for what it's worth. Why sho
by patrec 7y ago
Well, as long as we can agree that shitty bytecode interpreters are not the way to go ;)
I think AOT/JIT as a dichotomy is stupid, for what it's worth. Why shouldn't I have e.g. both profile guided optimization and JIT in the same program?
- pjmlp 7y agoThat we surely agree, interpreters are only good as one is ramping up a language. or doesn't plan to use it beyond basic scripting or learning activities. You can have both on the same toolchain, and plenty language do have them. However in some scenarios, like constrained embedded devices, you are left with AOT only. By the way, modern Android is all three, interpreter, AOT and JIT with PGO.