|
2010-09-28
, 16:41
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#472
|
I can only imagine that developers in general may be reluctant to target MeeGo with Android, iOS, and BBOS to consider. Of course, this is all hearsay.
The Following User Says Thank You to wmarone For This Useful Post: | ||
|
2010-09-28
, 17:14
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#473
|
Considering that none of those will appear on Nokia devices any time soon, whereas Qt will make software available across all Nokia devices within the next year I suspect that, unless they're a totally US-focused developer, they may target at least Qt if not MeeGo.
I just want another device like the N900, only with a better interface and better hardware.
|
2010-09-28
, 18:41
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#474
|
|
2010-09-28
, 20:39
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#475
|
|
2010-09-28
, 23:09
|
|
Posts: 857 |
Thanked: 362 times |
Joined on Feb 2009
@ London
|
#476
|
|
2010-09-28
, 23:38
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#477
|
I keep wondering if MeeGo will be arriving with too little and too late?
Things are snowballing between the 3-4 main camps as they engage with continuous cluster**** among themselves.
MeeGo will find itself in a highly competitive market, and I, like you, am curious to see what it will introduce that will be enough to differentiate it from its competitors.
I can only imagine that developers in general may be reluctant to target MeeGo with Android, iOS, and BBOS to consider. Of course, this is all hearsay.
|
2010-09-29
, 02:39
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#478
|
|
2010-09-29
, 09:58
|
|
Posts: 381 |
Thanked: 847 times |
Joined on Jan 2007
@ Helsinki
|
#479
|
Considering that none of those will appear on Nokia devices any time soon, whereas Qt will make software available across all Nokia devices within the next year I suspect that, unless they're a totally US-focused developer, they may target at least Qt if not MeeGo.
The Following User Says Thank You to bergie For This Useful Post: | ||
|
2010-09-29
, 10:07
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#480
|
Well a VM really is the only way to do it without cross compiling. So your choices are pretty much every scripting language, Java, and Microsoft's CLR. But then you toss in the mess of platform non-specific toolkits, so you might as well just use something like Qt and a good set of cross compilation tools.
PNaCl: Portable Native Client Executables
Google's Native Client technology uses software fault isolation (SFI) to enable the execution of untrusted native code inside a web browser, giving web applications greater access to the
performance of the client machine while avoiding the security problems with current infrastructure for plugins.
While the operating-system neutrality of Native Client tends to encourage good practices with respect to ISA portability, the burden of building, testing and deploying a program on all supported hardware platforms---currently IA-32, ARM and x86-64---lies with the developer. This arrangement makes it too easy for the developer to fail to support one or more ISAs, and tends to create a barrier for future new ISAs, threatening the portability
promise of the Web.
This document describes the design of PNaCl (pronounced "pinnacle"), a suite of tools for building, testing, and distributing Native Client programs in an instruction-set neutral format. PNaCl uses the Low-Level Virtual Machine (LLVM) bitcode format to represent ISA neutral portable executables compiled from code written in a variety of languages including C and C++.
The PNaCl design allows some flexibility in deciding where translation to native machine code occurs. By supporting client-side translation to the client's native instruction set, PNaCl reduces the burden on the developer, enabling support of new instruction sets without recompilation from the source. As PNaCl is layered cleanly on top of current ISA-specific NaCl implementations, the small trusted code base, source language neutrality, and safety properties of the system are preserved.
PNaCl, which will be open-sourced, is still at an early stage of development; we welcome feedback and suggestions on how its design might be improved.
Tags |
android envy, buzz..buzz buzz, core failure, crapdroid, galaxy fap, galaxy tab, ipad killer, samsung, tab trolls, tablet envy |
|
http://www.amazon.com/DURAGADGET-Res...5688117&sr=8-8
This is pretty neat, though I would love it if it were more fashionable and had a strap (I'm thinking more of a masculine sash than a man-purse.. lulz). I can foresee the time where I'll only need to carry the Tab with me, my trusty BT stylus, and a cable for charging, and I'd be ok with an ultra compact bag (especially in the winter when I've got a jacket on).