Oh man, we have struggled with this- and I wrote the copy under the Build / Compose / Run tab to try and surface what we felt were the most salient points.
For WebAssembly Components- we have tiny, portable code, with a standard ABI that lets us compose between languages. For execution, 50 ns start time means that you can start on demand 'with no cold starts'; the converse is true - scaling to zero.
Because you can scale it and run it only when you need to you can be more reliable (run it in more places) while still operating in a cost efficient way.
It's a subtle story that can be hard to communicate. Thank you for the feedback, we're always trying to do better.
For WebAssembly Components- we have tiny, portable code, with a standard ABI that lets us compose between languages. For execution, 50 ns start time means that you can start on demand 'with no cold starts'; the converse is true - scaling to zero.
Because you can scale it and run it only when you need to you can be more reliable (run it in more places) while still operating in a cost efficient way.
It's a subtle story that can be hard to communicate. Thank you for the feedback, we're always trying to do better.