Re: MeeGo's Community Woes
 

Well of course it isn't built completely from scratch. IIRC it still uses a standard linux kernel and some common APIs.

Re: MeeGo's Community Woes
 

I was still making reference to this operating system as an ARM Linux OS. It would seem terrible to write so much from scratch right away. Wasteful and dumb, really. Hopefully that's not the case--or if it is, it'll QUICKLY develop faster than Maemo did. God, it's been YEARS and Maemo STILL ended up feeling unfinished in its latest incarnation.

Re: MeeGo's Community Woes
 

It uses a ton of common code. Virtually everything that comprises MeeGo already exists, and that which doesn't is mostly reference code for UIs, or is external to MeeGo itself (drivers, firmwares.)

In fact, most of the work now is packaging and integration I believe, with some device-specific work being done by hardware adaptation teams (N900, Aava.)

Now if you want to talk about reinventing the wheel, that's when you look at Android ;)

Re: MeeGo's Community Woes
 

It should be clear to pretty much everybody by now that Harmattan is the old "Maemo6", development of which started a long time before N900 launch.

Re: MeeGo's Community Woes
 

Android did not only reinvent the wheel, they ensured that the wheel they came up with doesn't work on any of the existing roads.

Re: MeeGo's Community Woes
 

That's true! Ironically, it matured REAL fast. It probably helped that Google had a lot of money, engineers and actually COMMUNICATES with its intended vendors and developers who themselves bother to talk to their intended audience, the customers. Nokia never quite seemed to get a knack for any of this. I would have rather seen Maemo turn into the big success that Android has quickly become. Talk about your missed opportunities.

At this rate, where they're going, they aren't going to need roads. They're quickly flying above the rest.

Re: MeeGo's Community Woes
 

lemmyslender has the right idea. However, that isn't always as easy as it sounds :)

Challenges from merging Nokia's stuff:

* Moving platform components previously happily non-oss out in to the open (licensing process does take time, honestly, when you need to verify the resulting open source code is 'safe' from patent infringement possibilities, etc)
* Moving from a hardware specific focus to hardware agnostic focus in software/platform parts (we had a big deal of problems with that in MeeGo)
* Implementing UX different from Nokia's that is free from ties to let vendors customize
* Merging proper Qt + SDK parts like MADDE takes time to refit
* Retraining people for RPM packaging

Challenges from merging Moblin's stuff:
* GTK+ based and netbook-focused
* Previously fairly Intel-focused, even though ARM
* Making the architecture fit the MeeGo vision

... and most importantly of all: creating processes and get people working together.

So, no, not from scratch, but as with any merging in organisations, it takes a lot of frustration and leg work. We're quite far by now :)

Re: MeeGo's Community Woes
 

Actually, judging from Stskeeps' comments on the state of MeeGo on the N900 everything seems to be a bit further ahead than I realised.

I'm actually looking forward to the 1.2 release in April(?) now.

What I'm hoping to get out of MeeGo personally is a "purer linux" than maemo. E.g. proper bluetooth support for keyboards & mice and the ability to cross compile linux apps for the n900 unlike android.

Android is a great linux-based mobile platform but looks so "alien". E.g. no standard libraries mean cross-compiling linux software is almost impossible and means a re-write/re-implementation of existing linux apps. Of course there is that "paranoia" of how much information Google are taking from you too!

I think the next release of MeeGo is going to be the most important release so far - there's a lot to prove.

Re: MeeGo's Community Woes
 

I endorse this message. :) Particularly the 'purer linux' portion and the 'alien'ness of Android. I rather like Android a lot right now, but as I already said for years about Maemo, "if something better comes along, I'm perfectly willing to jump ship--I don't consider myself married to a platform like a lot of fanboys." If MeeGo can impress me and include the features you're suggesting, I will probably jump ship again to MeeGo. Mind you, I'm far more likely to try Intel's solution since I'm skeptical of Nokia's motives after my incredibly negative experiences dealing with them and their hardware support is literally an appalling exercise in futility and insult.

Anyway... here's hoping the best for MeeGo!

Re: MeeGo's Community Woes
 

Amen to that :D

Re: MeeGo's Community Woes
 

My tought is, where is the big blog news? None of the big tech blogs seems to have written about meego in a while. As for avaa, two problems. 1. X86. 2. Not generally available!

Re: MeeGo's Community Woes
 

the only that is written from scratch is the UI layer. and some of the security framework as far as I know. But it probadly enought to make it not be release any handsets before Q3.

and about android "hack" what I meant is that Android was first done for small screen then they upgrade in every release support for bigger screens etc...

I am not and expert but to me it looks like QtQuick can be better than Android/Ios and simpler for app developers making multiplatform UI for both tablets/handsets and stationary computers. Also Nokia/intel and other Meego developers has now the possibility to see the mistakes done in Iphone/Android and make it better in Meego :D and that sometimes is missed point by many of those who says "Nokia should go Android"

Maybe I am following qtquick and its development to much but too me its seems very promising atleast :)

Re: MeeGo's Community Woes
 

ofcourse they dont. Same thing as when Android was in betastage. The media is just doing as always following the mainstream and whats make them most profit atm...