Linked by Thom Holwerda on Tue 8th May 2012 11:56 UTC, submitted by nej_simon
Tizen reached 1.0 only recently, but there's already a Tizen Conference going on - and during that conference, Samsung had a relatively barebones reference device running Tizen 1.0. The Handheld Blog has a seven minute video of the device in action, and while I'm very happy big players are investing in all these alternative platforms, I do have to wonder - how viable are they?
Thread beginning with comment 517334
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: It all comes down to price
by shmerl on Tue 8th May 2012 19:44
in reply to "RE[2]: It all comes down to price"
Member since:2010-06-08
RE[4]: It all comes down to price
by zima on Tue 8th May 2012 21:09
in reply to "RE[3]: It all comes down to price"
Member since:2005-07-06
That's why Qt won't be replaced by JavaScript
That's a bit of a misnomer, since (essentially...) JavaScript can and is used in tandem with Qt, even (especially?) in mobile setting:
http://qt.nokia.com/qtquick/
http://en.wikipedia.org/wiki/Qt_Quick
http://en.wikipedia.org/wiki/QML
(and it's of course stillborn, with Nokia going Windows Phone; but the fabled Meltemi should have it)
PS. Hm, it seems you added "pure" in between me clicking reply, and finally getting down to finishing my comment
Edited 2012-05-08 21:11 UTC
RE[4]: It all comes down to price
by zima on Tue 8th May 2012 21:11
in reply to "RE[3]: It all comes down to price"
Member since:2005-07-06
Member since:
2005-09-01
I agree, mass OEM producers are most specialized on cost cutting and they will go the path of least resistance when choosing the SW platform and that most likely means standardizing on some light modification of Android.
But Samsung is in other game now. They will keep investing in Tizen and use that to keep Google and Microsoft in check. Commoditizing APIs is a dream shared by both carriers, HW devs and developers (look how much effort is wasted in redoing the same SW for IOS, Android, Symbian, Java, Bada, WP and whatnot?). Even Google would probably benefit in the long term. Only Apple and Microsoft would be hurt with their developer locking abilities diminished.
The problem is, no feasible technical solution is in place. HTML5 is not going to be the answer until either I5 level of processing power is available in mobile devices within $100 price range or major performance boost in JS jit technology is around the corner, or some breaktrough in battery tech that would allow Intel to put I5 proper in a mobile phone. Given how many years it took Intel to reach that and that scripting lang. have been around for couple of decades with JIT work ongoing the last is only remotely likely proposition.
Edited 2012-05-08 17:18 UTC