3 ms·
> Running Python securely on a local machine is a really hard problem. We treat all Python code in the workbook as untrusted, so we execute it in a hypervisor-i
by SenAnder 3y ago
> Running Python securely on a local machine is a really hard problem. We treat all Python code in the workbook as untrusted, so we execute it in a hypervisor-isolated container on Azure that does not have any outbound network access.
I see we've moved on from "we have to lock down computers against the user with no way to circumvent it because otherwise the user might install a virus" to "it's really hard to set this up locally, so we did it on a server, which is special and magical and things are easier there than on user PCs where containers do not work."
I eagerly await "Font rendering is a really hard problem. To assure perfect results, all document text and monitor configuration data is sent to Azure, where we can take advantage of the most up-to-date rendering algorithms, reliable GPUs, and updated font files, to efficiently produce .png files that the user's machine displays."
- RodgerTheGreat 3y agoIf Microsoft genuinely cannot figure out how to sandbox a python interpreter on Windows, with access to functionally unlimited funding and resources, it is a scathing indictment of their engineering teams, their OS, or both.
- chrisjj 3y agoThis does presume that PNG display can be entrusted to the local machine ...