View Single Post
Posts: 347 | Thanked: 441 times | Joined on Dec 2010
#21
Originally Posted by onethreealpha View Post
Here's some more important questions:

Is it Arm or x86?
what is the hardware design? who doing the CAD and electrical schematics for the mainboard and SoC stack?
Who's doing the hardware adaptation for whatever product you want to put Maemo on?
If you're getting drivers from the h/w vendor, will they guarantee support and updates (since it's now out of your hands?) and at what cost? Or will they drop any and/or all support when THEY move to another SoC/chipset/GPU...
Who's going to work on and bugfix all the forked stuff that can't easily be replaced without major re-working of the OS?
who's going to do the UI adaptation for the screen resolution?
who providing the updates for coreOS.
who's going to set up and host the repo/
who's going to maintain, log and fix bugs?
who's going to get existing apps modified to run on the new screen resolution?
What IDE are you going to use for dev work?
Who will provide software builds for emulation?

shall I go on?

...better off waiting for Vivaldi tab and then work to replace plasma active with Hildon
Nope. So you should never start building something?
Most of those things can be done buy many people. But very few companies are willing to sell you a good cpu if you don't buy large enough.

And how much longer is the wait for the Vivaldi?
__________________
Motorola M3688 → Ericsson R320 → Siemens S40 → Motorola V60c → Palm Treo 650 → Blackberry 9000 → Nokia N900 → HP Pre 3 → Nokia N900 → Nokia N9 → Nokia N900 → Nokia 808 → Blackberry Z10 → Blackberry Passport

Only dead fish swim with the stream.
 

The Following User Says Thank You to The Wizard of Huz For This Useful Post: