Just checked the tivoization definition. (Guess I should have done so, when reading the original thread, when I felt unsure from their explanation of the word).
So, it has to be runnable on the same hardware after modification. It makes sense now.
I seems like something that would be good in case the solution is being used for a long period and would make sure the user doesn’t have to bear the burden of finding another platform that would run the binary, in case a library update is required. This would be in the interest of even corporate clients.
Yeah, I thought so too.
Guess the V3 has some major, thoughtful changes.