View Single Post
nicolai's Avatar
Posts: 1,637 | Thanked: 4,424 times | Joined on Apr 2009 @ Germany
#88
Originally Posted by qgil View Post
The developer community can contribute to community projects under development with a good chance to become a top notch media player, a top notch calendar, etc. The frameworks and APIs are all there - I would argue that the candidates as well.

You have the KDE mobile developers, the Qt Quick app developers, the Python+Qt developers, the traditional Qt developers, the new MeeGo... all of them with interesting projects in the hands and looking for contributions. Is there any reason in the N900 hardware and the Maemo 5 software to stop that coolness? Honestly, I don't see it.
These are all valid points. And I wish this projects great success, not
for maemo, not for meego or nokia, just because I prefer open developed alternatives.
But this raises the question:
Why nokia can not adopt this for its own products?

In my opinion, developing and producing an open OS based, open
community supported device and deliver it with closed source application
is a big mistake.
It was a mistake for the Nokia 770, N800, N810 and N900.

I don't say I expect to get all software for free or open. I don't say
we deserve to get this closed parts open. But I think it was a mistake
and hoped nokia could correct this.

I follow the meego handset UX development and asked for the
application specifications, I hoped the community could help to
not repeat nokias Maemo5 mistakes (missing functions in applications,
like contacts, phone-ui, calendar ...)
This was before I realised the first "meego" device won't use meego handset UX,
but instead nokias applications are developed behind closed doors again.

There is so much power in this community. Honestly, I don't see
any advantage in developing again those applications as closed source components.
Nicolai
 

The Following 8 Users Say Thank You to nicolai For This Useful Post: