Linked by Thom Holwerda on Mon 14th May 2012 15:20 UTC
Windows "Senate Judiciary Committee staffers plan to take a look at allegations that Microsoft has made it difficult for competing Web browsers to run on a certain version of Windows, an aide to Antitrust subcommittee Chairman Herb Kohl told The Hill Thursday." Good. We have to nip this in the bud, and with a bit of luck, it alerts Washington to the iOS situation as well. More browser competition equals a better web - mobile devices aren't magically exempt from this just because they have no keyboard. As simple as that.
Thread beginning with comment 518163
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: On the other hand
by pgeorgi on Tue 15th May 2012 07:42 UTC in reply to "On the other hand"
pgeorgi
Member since:
2010-02-18

On the other hand it is a rather bad idea to in law enforce that all operating systems has to provide arbitrary applications with simultaneously writable and executable memory. There is certainly a huge security advantage to banning it.

They don't provide the CLR compiler to metro apps on ARM as well.
That could be a middle ground: let Firefox et al compile Javascript to CLR, then let Microsoft's own JIT take care of security and speed.

It's allowed to use the JIT on x86, but not on ARM. It's all about iOS-style lock-in (you can't easily run downloadable code that way).

iOS was an oversight (who would have thought that Apple creates a hit?), but Microsoft is usually market leader by "Version 3".

The iOS lock-in should be fixed, the Metro lock-in avoided. No need to repeat making mistakes.

Reply Parent Score: 2

RE[2]: On the other hand
by vaette on Tue 15th May 2012 11:14 in reply to "RE: On the other hand"
vaette Member since:
2008-08-09

That is an interesting fact, and I agree that this would be a very good middle ground. Possibly restricting the code you generate to the JIT to be run in a secure context as well. Hopefully Microsoft can pick up that idea.

Reply Parent Score: 2

RE[3]: On the other hand
by pgeorgi on Tue 15th May 2012 12:15 in reply to "RE[2]: On the other hand"
pgeorgi Member since:
2010-02-18

That is an interesting fact, and I agree that this would be a very good middle ground. Possibly restricting the code you generate to the JIT to be run in a secure context as well. Hopefully Microsoft can pick up that idea.

They already support that, on x86. They presumably support JIT on ARM, too (.net stuff would be very slow on that platform, giving it a bad reputation).

As for restricting the code pushed into the JIT, that's a standard feature on Java and .NET since 1.0.

So until they clear this up, I consider it a deliberate limitation on ARM where it's all about lock down.

Reply Parent Score: 3