Linked by Thom Holwerda on Sun 11th Mar 2012 22:21 UTC
Windows And thus, Microsoft bites itself in its behind with Metro. As you all surely know by now, the Metro environment in Windows 8, and its accompanying applications, need to follow a relatively strict set of rules and regulations, much like, say, applications on iOS. For one type of application, Metro has already proven to be too restrictive and limited: web browsers. Microsoft has had to define a separate application class [.docx] - aside from Metro and desktop applications - just to make third party web browsers possible for Windows 8.
Thread beginning with comment 510298
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: I think
by Nelson on Mon 12th Mar 2012 12:57 UTC in reply to "RE[5]: I think"
Nelson
Member since:
2005-11-29

They already are, they use Microsoft's memory mapping APIs for their JITs, so they're tied to Win32.

The difference would be that this would be an runtime verified versions of these APIs, which, given the circumstances is an acceptable cost.

JIT engines have farther reaching implications than JavaScript compilation, for example, many Game Engines JIT compile their scripting languages. So obviously, a more general solution is needed. They can't keep carving out exceptions for apps.

Reply Parent Score: 2

RE[7]: I think
by zlynx on Mon 12th Mar 2012 15:22 in reply to "RE[6]: I think"
zlynx Member since:
2005-07-20

But if Microsoft allows JIT their app store cannot do any meaningful inspection of the software for malware or bad behavior.

Allowing the program to modify machine code or generate entirely new machine code means that it could do anything.

Reply Parent Score: 2