Linked by Thom Holwerda on Sun 23rd Sep 2012 01:05 UTC
Mozilla & Gecko clones "It's no secret that Mozilla has been working on a mobile OS. Previously codenamed Boot2Gecko, the project focused on a purely HTML5 based system that worked in many ways like current mobile devices. As the project grew into Mozilla OS, the company has laid out a partnership with ZTE that will have real world devices in certain markets early next year. Testing for this OS had previously consisted of a compiled ROM that would be flashed over a handful of Android devices. Now, Mozilla has moved into full fledged product evaluation mode with their own custom developer phone." Looks decent - and a better solution for testers and developers than custom ROMs.
Thread beginning with comment 536193
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Will not work.
by reduz on Sun 23rd Sep 2012 19:33 UTC in reply to "RE: Will not work."
reduz
Member since:
2006-02-25

No, it _doesn't_ matter at all. "ready" is too broad of a term and irrelevant to this situation. Let's recheck history.

-Palm moved from m68k to ARM, tried to still promote m68k development by running it in an emulator. Failed, developers preferred native. Then PalmOS6 was supposed to be native, but good old Palm died.
-J2ME sucked, no one did anything woth playing for it.
-WebOS was html based, developers didn't like it and pushed for native. Finally native was allowed but it was too late.
-XBox Indie Arcade is .net only, totally flopped. XBLA is native, was successful.
-Nintendo tried something similar by allowing you to run javascript games in the browser, failed.
-Nokia n-gage was java, failed.
-iPhone was also supposed to be html5 only based, developers complained and then went native.
-Android was Java only, developers complained and Google had to release the NDK.
-Microsoft released WP7, .net only, flopped. WP8 is native.
-Flash is ActionScript, now when fading in popularity, Adobe concedes and goes native with Alchemy.

After ALL THIS, Firefox has the balls to go and announce their HTML5-only based phone.
I'm sorry, denying developers of native access simply doesn't work. It never did. It's been proven again and again and again ad infinitum. C is still the most popular programming language, period. It's one of those things that shouldn't be that difficult to understand by most people and companies, yet they keep thinking they can reinvent the wheel.

Edited 2012-09-23 19:35 UTC

Reply Parent Score: 0

RE[3]: Will not work.
by Nelson on Sun 23rd Sep 2012 19:52 in reply to "RE[2]: Will not work."
Nelson Member since:
2005-11-29

WP7 has over 100k apps. In who's reality is that a failure ?

Also WP8 will still primarily use C# with C++ being used by games and for WinRT components.

In Windows 8 where devs can use C++, 80% of Store apps are C# and XAML based.

As someone who participated in XBLIG, the problems was not the choice of C#, but rather boneheaded decisions by Microsoft with regards to cost, agility, and awareness. It was just a very badly run program.

Reply Parent Score: 2

RE[4]: Will not work.
by reduz on Sun 23rd Sep 2012 20:34 in reply to "RE[3]: Will not work."
reduz Member since:
2006-02-25

Who cares about the amount of apps? Blackberry app world had plenty too. Quality is what matters and WP7 was a flop. The fact is, Quality apps and games are almost always native. It's a rule.

Reply Parent Score: 1

RE[3]: Will not work.
by Lennie on Sun 23rd Sep 2012 22:55 in reply to "RE[2]: Will not work."
Lennie Member since:
2007-09-22

A lot has changed and almost any API Mozilla makes for Firefox is also proposed at the W3C and discussed there to be specified as a proper standard.

Which means even if Firefox OS does not work out, all the APIs will be made available for others to work on (so the new Tizen, WebOS or whatever does not have to reinvent the wheel).

It also will allow browsers to adopt these standards.

Pretty much everything you can imagine has al ready been standardised, proposed as a standard or is being heavily worked on.

Just have a look at WebRTC for example.

There has been massive leaps since Apple tried to promote WebApps

Edited 2012-09-23 22:58 UTC

Reply Parent Score: 2

RE[4]: Will not work.
by swift11 on Mon 24th Sep 2012 03:04 in reply to "RE[3]: Will not work."
swift11 Member since:
2012-08-23

There has been massive leaps since Apple tried to promote WebApps


Agreed. River Trail is an interesting project, for instance:
https://github.com/rivertrail/rivertrail/wiki

Reply Parent Score: 1