2 ms·
They're not banning it. They're just not allowing access to critical API functions for a JIT engine to Windows Marketplace apps. Only IE has access to it. Wi
by TimGebhardt 14y ago
They're not banning it. They're just not allowing access to critical API functions for a JIT engine to Windows Marketplace apps. Only IE has access to it. Without these APIs then Firefox will run like a dog because it'll undue all the years that people have been working on optimizing Javascript engines.
- jack-r-abbit 14y agoRight. So... I don't ban anyone from my swimming pool... everyone is welcome. But if you're not family, you have to wear this 100lb ankle weight. Dive right in everybody! lol
- stan_rogers 14y agoA more apt analogy would be to require everybody to wear a life jacket and a bike helmet. You can do whatever you want, as long as it's safe.
- TimGebhardt 14y agoI think there is a big difference between banning it outright (like Apple) and hampering it. From the end-users point of view both suck, but at least if I use Firefox to sync my bookmarks and passwords I'm able to on a Windows tablet. Nothing I can do on an iPad.
- jack-r-abbit 14y agoFirst, let's assume the majority of users are not going to know why the an app is not allowed and/or why it is sluggish/limited/hampered/etc. From the average user point of view... the biggest difference to me is that when it is banned, the banner (Apple) is the bad guy for not letting it in. When it is severely hampered the bad guy appears to be the creator (Firefox) for making a crap app when in reality the hamper-er (Microsoft) is the bad guy for crippling the app's ability to perform as well as it can.