Hacker News new | past | comments | ask | show | jobs | submit login

> Also for Apple to allow v8, they would have to permit 3rd party unsigned executable code (JITed in this case). Apple doesn't want to allow that.

And how does that pertain to security? Android doesn't seem to have a problem with JITed code in sandboxed store apps. Neither does Win10.




Actually UWP does not allow for JIT code, other than Chackra, as you should know.

Hence MDIL in WP 8.x and .NET Native on WP 10 onwards.


WinRT sandbox has always allowed for JIT'ted code, all the way back to the original Windows 8 release - all .NET Store apps back then were running on a JIT. .NET Native is a later addition that is there solely to improve performance, and it is still opt-in.

Now, Win8.x did not allow for third-party JIT compilers in the sandbox; it was only CLR or Chakra. But UWP does - look for the "codeGeneration" capability here:

https://docs.microsoft.com/en-us/windows/uwp/packaging/app-c...


WP 8.x did not JIT code on device, hence the whole MDIL and cloud compiler on the store.

WP 8.x only did dynamic linking at installation time and when OS updates were done, by replacing symbolic labels with the actual target destinations. Everything else was already compiled at the store and downloaded as binary into the devices. This was the whole point of MDIL.

There is a BUILD session and a further Channel 9 deep dive interview showing how MDIL deployment works on WP 8.x.

So Chakra was the only JIT in town.


Since the comment does not allow for editing any longer.

"BUILD 2012, Deep Dive into the Kernel of .NET on Windows Phone 8"

https://channel9.msdn.com/Events/Build/2012/3-005

"Mani Ramaswamy and Peter Sollich: Inside Compiler in the Cloud and MDIL"

https://channel9.msdn.com/Shows/Going+Deep/Mani-Ramaswamy-an...


Oh, I meant Windows, not Windows Phone (for 8.x, that was a big difference still).

Either way, code generation is there today.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: