|
2010-06-02
, 07:28
|
Posts: 81 |
Thanked: 44 times |
Joined on Nov 2009
@ Switzerland
|
#82
|
|
2010-06-02
, 07:48
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#84
|
Well you knew it, I knew it, who the heck didn't know it? So why you insist him to say it? But Android isn't the only one. Bada - is it more open than Meego/Meamo? Android for sure isn't.
|
2010-06-02
, 08:58
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#85
|
|
2010-06-02
, 09:19
|
|
Posts: 2,361 |
Thanked: 3,746 times |
Joined on Dec 2007
@ Berlin - Love this city!!
|
#87
|
|
2010-06-02
, 12:46
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#88
|
Seriously. Is it that hard to just say that?
I know to the Nokia faithful, my questions will be somehow foolhardily relegated to "attacking" but while Qgil is answering questions, I would love to see (from Nokia's standpoint) what they have planned to make MeeGo a viable product to those of us with so much invested into Maemo in terms of non-developers.
Sure, I mean from the technical side, Qt is wonderful. The move to *.rpm from *.deb, while argued plenty in the past just means a few changes in mindset in regards to installing things. I get that.
But on a much lower level, the consumer... what's so different? On some days, I don't want to hear lofty or overly technical terms on how something I've foolishly come to depend upon (my cellphone) can extrapolate portions of the human genome if I program it in Python and use a certain library... I just want to know what compels that company to solve some of my lesser needs.
Or why I should support them.
I'm already here. I've bought two Maemo devices. I've contemplated a third. I'm on the cusp of the Maemo to MeeGo transition and the technical side of me is still researching. The consumer side needs more reassuring.
Thus... my questions.
The Following 2 Users Say Thank You to SD69 For This Useful Post: | ||
|
2010-06-02
, 21:16
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#89
|
Reading you it looks as if Nokia would be an enemy of openness of sorts. Yet...
What commercial handsets can you find in a shop more open than the Maemo devices?
How many companies can you list contributing more open source code and features? (Maemo/MeeGo + Symbian + Qt)
What commercial mobile platforms can you list with a more open setting and approach than the platforms where Nokia is involved? (MeeGo, Symbian)
Nokia is not perfect in terms of free software development but at least is trying hard investing a huge load of resources and publishing a huge load of new code available for anybody. Show us concrete alternatives that are succeeding commercially with a more open approach and we will seriously consider them (if we are not doing it already).
If you're going to refer to Ari Jaaksi's infamous quote, it had a larger scope than that. He was referring to a closed (ironically) mindset that keeps Linux from being a greater success, and that was the reluctance to at least meet business halfway and understand profit drivers instead of vilifying them as something inherently evil.
Ultimately neither Nokia nor any other company can operate for free. Nokia has decided, wisely IMO, that there's no longer enough value to be found in being an operating system provider. So they will focus on their technological (and hopefully, service) advantages as those profit drivers. If every aspect of hardware is opened, and that hardware becomes commoditized, where does Nokia derive revenue in this space?
Let's see how Pandora fares and then cast stones at Nokia if they are successful.
disclaimer: I would personally love to see mobile computers ultimately commoditized to the point that PCs are. I build all of my PCs.
gerbick, I'm comparing Nokia with the companies you compare Nokia all the time and with the products available in the shops where you can find Nokia products. If you don't like this comparison please propose another one.
About BME closed, did you go and ask at meego-dev as I proposed to you few days ago when you came with the same point in this forum?
About the MeeGo architecture, http://meego.com/developers/meego-architecture shares a lot with Maemo, with Moblin and with other distros. Yet is a stack that it's not Maemo' it's not Moblin, it's not Fedora/openSuSE/Ubuntu/Debian. If you understand a bit about Linux platforms you will see that it's a quite unique and innovative stack having to solve certain problems other distros don't attempt to solve.
And sure, there are plenty of companies and even more individuals and also non-profits contributing LOTS of code and more. I'm not dismissing any of them! I'm just defending that Nokia is one of these organizations, actually contributing a lot. And again, if you go and ask Linux and free desktop developers and maintainers you will see that all in all Nokia gets better than worse feedback about what we do and how we do it.
About the lessons learned, I think in every Maemo iteration there were improvements but there was a structural ceiling barring more significant progress. This is one of the reasons why MeeGo was created, and Nokia is applying the remaining reasons there.
PS: the more you discuss about the MeeGo project the more it makes sense to do it at http://forum.meego.com
Probably he was answering partly to me to. I think it's useless to send us to meego forum, as now we are talikng about nokia meego and maemo, and it touches some aspects of maemo community as well. And as gerbick, i don't see any straight answer or fact, i just see the reflecting answers. As well i would like to here how can people really can be involved in maemo development, and when i talking not about applications, i'm talking about bug fixes(as some code is closed or i had personally met the problem when bug was refused to open as it was mark as fixed, but it's still there), what are the point of bug reports if they are not comming straight and we don't really know if they are fixed, as well i would like to know how community can get the roadmap of development, there are a lot of question people asking at forum everyday and as i saw Nokia if gives answers - it's only to certain questions they want and even than no 100% info.
Read this, it might help:
http://www.nokia.com/NOKIA_COM_1/Tec...hite_paper.pdf
MeeGo OS will be more or less open, but the MeeGo devices that Nokia sells will have differentiating UI, apps and services.
The Following 4 Users Say Thank You to danramos For This Useful Post: | ||
|
2010-06-02
, 21:44
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#90
|
We can't discuss concrete details about what is different in a MeeGo product from a consumer perspective before there is a Handset UX published and at least one MeeGo handset product announced by a vendor.
The Following 2 Users Say Thank You to Texrat For This Useful Post: | ||
I know to the Nokia faithful, my questions will be somehow foolhardily relegated to "attacking" but while Qgil is answering questions, I would love to see (from Nokia's standpoint) what they have planned to make MeeGo a viable product to those of us with so much invested into Maemo in terms of non-developers.
Sure, I mean from the technical side, Qt is wonderful. The move to *.rpm from *.deb, while argued plenty in the past just means a few changes in mindset in regards to installing things. I get that.
But on a much lower level, the consumer... what's so different? On some days, I don't want to hear lofty or overly technical terms on how something I've foolishly come to depend upon (my cellphone) can extrapolate portions of the human genome if I program it in Python and use a certain library... I just want to know what compels that company to solve some of my lesser needs.
Or why I should support them.
I'm already here. I've bought two Maemo devices. I've contemplated a third. I'm on the cusp of the Maemo to MeeGo transition and the technical side of me is still researching. The consumer side needs more reassuring.
Thus... my questions.