Yeah it's a bit weird to see the difference. > Also, ExecuTorch does not rely on TorchScript, and instead leverages PyTorch 2 compiler and export functionality

Yeah it's a bit weird to see the difference. > Also, ExecuTorch does not rely on TorchScript, and instead leverages PyTorch 2 compiler and export functionality for on-device execution of PyTorch models. I think this is the major change: AFAIU you could consider ExecuTorch as ""just a rewrite"" of PyTorch mobile using PyTorch 2 compiler. BUT this is should still be pretty major. It was pretty hard to retarget models to be compatible with TorchScript. But most recent models will want to target PyTorch 2 compiler for the performance boost. Which means they'll automatically get ExecuTorch support. As someone who got burned several times in trying to port models to TorchScript and run them on Androids, I'm happy they did that.