Linked by Kroc Camen on Tue 23rd Mar 2010 08:25 UTC
Mozilla & Gecko clones It has long been known that in addition to the N900 port of Firefox (released just 49 days ago) Mozilla have been targeting Windows Mobile, drawing ever nearer to a release. They have now decided to put the port on hold, following the news of Windows Phone 7 Series at MIX (and what that holds for Windows Mobile 6.5). "While we think Windows Phone 7 looks interesting and has the potential to do well in the market, Microsoft has unfortunately decided to close off development to native applications. Because of this, we won't be able to provide Firefox for Windows Phone 7 at this time. Given that Microsoft is staking their future in mobile on Windows Mobile 7 (not 6.5) and because we don't know if or when Microsoft will release a native development kit, we are putting our Windows Mobile development on hold."
Thread beginning with comment 414910
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Kroc
by BluenoseJake on Tue 23rd Mar 2010 15:17 UTC in reply to "Comment by Kroc"
BluenoseJake
Member since:
2005-08-11

I did want to make this a pg.1, but I don’t have the time right now, and I’m weary of overloading the home page with web news (rather than traditional OSes).

I just want to add that this is sad, but a clear sign that the web browser is becoming a core part of the operating system and that the vendors don’t feel that it needs to be replaced (which would prevent them from from getting the tightest integration with the system).

It’s like when TCP/IP stacks used to be separate, and now they’re just an expected part of the OS, embedded very deeply.

Mozilla are unfortunately being denied access to the mobile world and I really don’t see this changing unless they make Gecko more fun to port. WebKit is owning this space.


Everybody is being denied access, until a native SDK is released. Saying it like that makes it sounds like a conspiracy.

Reply Parent Score: 3

RE[2]: Comment by Kroc
by Kroc on Tue 23rd Mar 2010 15:45 in reply to "RE: Comment by Kroc"
Kroc Member since:
2005-11-10

Nope, I don’t think it’s a conspiracy at all. I literally think that the browser is becoming such a core part of mobile OSes that allowing alternate browsers only undermines the value of the platform (that is, in the vendor’s eyes).

Nobody would want to run Firefox in a tab inside Chrome OS when Chrome OS itself is already a browser, and if Firefox could be offered it would undermine the APIs Google have added to to integrate the web with the device / UI.

Reply Parent Score: 1

RE[3]: Comment by Kroc
by Toonie on Tue 23rd Mar 2010 16:00 in reply to "RE[2]: Comment by Kroc"
Toonie Member since:
2007-11-19

Nobody would want to run Firefox in a tab inside Chrome OS when Chrome OS itself is already a browser, and if Firefox could be offered it would undermine the APIs Google have added to to integrate the web with the device / UI.


Hmm, integrating a browser right inside the OS.. I wonder what the EU would have to say about that?

Edited 2010-03-23 16:00 UTC

Reply Parent Score: 2

RE[3]: Comment by Kroc
by kaiwai on Wed 24th Mar 2010 02:34 in reply to "RE[2]: Comment by Kroc"
kaiwai Member since:
2005-07-06

Nope, I don’t think it’s a conspiracy at all. I literally think that the browser is becoming such a core part of mobile OSes that allowing alternate browsers only undermines the value of the platform (that is, in the vendor’s eyes).

Nobody would want to run Firefox in a tab inside Chrome OS when Chrome OS itself is already a browser, and if Firefox could be offered it would undermine the APIs Google have added to to integrate the web with the device / UI.


Assuming that is the case; from what Microsoft has said, they're going to have native API's but they're going to be a very small subset when compared to 6.5 - so it'll be enough for the likes of Flash to get their stuff working but if you're expecting the operating system to provide a lot of API's then you'll be disappointed. In the case of Firefox there is a good chance that many of the API's they rely on in 6.5 will be unavailable thus require them to implement the feature themselves instead of relying on the operating system.

Reply Parent Score: 2