![]() |
2011-01-22
, 14:59
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#42
|
Except from one case: Future devices. Android apps are guaranteed to run on future devices as long as they run a compatible OS version and most probably they will run faster and take advantage of the new hardware.
But when using MeeGo, who will dare (or care) to introduce a new architecture or improved hardware? It's not only a matter of architecture. Even an improved instruction set or extra registers will be useless if you have the same binaries, just like it happens with Debian (all programs are compiled for ridiculously old hardware).
![]() |
2011-01-22
, 15:01
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#43
|
I Can see V13's point very clearly, As a former N900 owner, and a Former Maemo Qt developer, Now an android owner and developer,
I can already feel how much easier maintaining an android app is - compared to a C++/Qt application, and also how much more rewarding it is.
Personally as a developer, I don't want to have to test and own 5 different devices just to be able to check if my compiled binary file really runs on all different 5 architectures.
![]() |
2011-01-22
, 15:11
|
Posts: 376 |
Thanked: 511 times |
Joined on Aug 2009
@ Greece
|
#44
|
Soo are u saying dalvik doesnt need those registers or what? Or are you saying. dalvik just found the new hardware and optimize it right away wihout a need toouch the code in dalvik codebase?
You have the same problems in Android too.
![]() |
2011-01-22
, 15:13
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#45
|
![]() |
2011-01-22
, 15:15
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#46
|
But when using MeeGo, who will dare (or care) to introduce a new architecture or improved hardware? It's not only a matter of architecture. Even an improved instruction set or extra registers will be useless if you have the same binaries, just like it happens with Debian (all programs are compiled for ridiculously old hardware).
![]() |
2011-01-22
, 15:20
|
Posts: 671 |
Thanked: 1,630 times |
Joined on Aug 2010
|
#47
|
... if releasing new, incompatible hardware were as much a problem as you are worrying about, companies like Intel and Mips would have shut their doors decades ago.
The Following User Says Thank You to theonelaw For This Useful Post: | ||
![]() |
2011-01-22
, 15:20
|
Posts: 724 |
Thanked: 1,255 times |
Joined on Nov 2007
@ Cambridge, UK
|
#48
|
![]() |
2011-01-22
, 15:21
|
Posts: 376 |
Thanked: 511 times |
Joined on Aug 2009
@ Greece
|
#49
|
Congratulations! (But are you really interested in only developing apps for one platform? If you, for example, wanted to port one of your apps to iOS, would that mean you'd drop all support for Android? I'm just kinda surprised at the implicit statement here that developing for one platform means not developing for any other platform.)
So, you are going to just assume that your app works fine on both Android phones and on Android tablets?
![]() |
2011-01-22
, 15:28
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#50
|
The Following User Says Thank You to mikecomputing For This Useful Post: | ||
![]() |
Tags |
bada rox, dalvik, future, java haters, meego, meego?fail, nokia, sandbox sucks |
|
Would this be possible for MeeGo? Such a port instantly makes available all android programs. Would mips care to port MeeGo? Would anyone care using MeeGo on mips devices (since there would be no available apps and not available central app repository)?
And finally... Was/Is this considered by Nokia/Intel?