"...as much as possible". That's exactly it. Mer shows the closedness of Maemo. The browser was Tear because the browser UI is closed in Maemo, the connection manager was NetworkManager because Nokia's ICD2 and libconnui are closed, Powerlaunch had to be used because both MCE and System UI are closed source. None of these performed as well as the equiv. Nokia closed component. Hildon Desktop was built for it by removing the IPHB code (done wrongly, BTW: it should've called the GLib function adding the timeout source) and a newer Hildon Application Manager couldn't be built because it depended on a closed libtime-dev. As for the rest, I don't think Mer got far.

Nokia were happy to say that a Fremantle-like OS produced by the community will allieviate the need for them to bring updates themselves with the FiF fiasco, but, yet, they're not happy to give up their code (in the case of Diablo, code that is neither used nor updated) for the community. Hint: The community (excluding the members who like to be raped by Nokia and will come up with excuses for it) don't like double standards. I mean you're happy to put out that 80 percent of Maemo is open source. Well, that figures - most of that percentage consists of open source code not written by Nokia.

@gazza_d

Agreed. Maemo will die. There's only so much free components that you can bring updates to. Sooner or later, at least one of Nokia's many closed source components will break.