x86 emulation is nice to have for running old x86 software that never got ported natively to ARM on Surface tablets. (Visio to name just one). Would I have to install some form of AV to block x86 code from breaking out into the ARM filesystem?
That's one reason I dislike non-Windows Store (unsigned/sideloading) of potential threats.
Thanks Rick, This parallel work that you're all working on is fantastic. Abstracting away the hard parts is definitely going to bring great benefits to all developers, and not just a minority in academia. I trust your making some progress with the parallel breakpoints problem.
How much of this work has been put into Azure?
Are you focusing on native first or going forward in parallel (no pun intended) with managed languages?
I don't generally code in C++ as such, I was just wanting to clear up a couple of questions.
In the video you mentioned that pointers should be discarded as soon as they are passed on to the next agent, and in one of the examples given for an x MB image file the pointer would be handed off from one to the next, and discarded en-route. Where does
the responsibility lie for releasing the storage pointed to by the pointer?
You have based this on the dataflow model of computation. Yes? If so, and this is sort of related to the previous topic, what would be the best approach for handling persistent storage, and/or shared memory?