It strikes me that there's a duality of sorts in any kind of remote application:
* the app stays on someone else's computer, you send your data to it: PRIVACY RISK
* the app comes to your computer, you run it there: SECURITY RISK
I think #2 is the best option, because once you send data anywhere you have lost all privacy forever, while you can restrict what foreign code does
but to get there, we need to have languages which are *really* secure against arbitrary untrusted foreign code.
Right. Emulators are good because they're not subject to the (pure) Halting Problem, because it's knowable what the emulator can (and especially what it can't) do.
If you have some kind of emulator or debugging mode or kernel or hypervisor, you're no longer an unrestricted Turing Machine scrolling off to infinity. The computation CAN and WILL halt because the outermost loop will go 'nope, that's enough CPU cycles for you' and pull the brakes.
A fun, happy little Mastodon/Hometown instance. Join us by the fire and have awesome discussions about things, stuff and everything in between! Please read our rules before doing that, though; applications without the password that confirms you have done so will be rejected. Admins: Talon and Mayana.