|
2011-09-29
, 10:05
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#42
|
|
2011-09-29
, 17:57
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#43
|
You're talking about different they's than me. I commented on the origins of this thread where community members throws a few dollars on the table and expects to be able to buy all of Maemo.
The Following User Says Thank You to danramos For This Useful Post: | ||
|
2011-09-29
, 18:03
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#44
|
I thought MeeGo was just EOL'ed. While it is newer, why is that any better? Wouldn't Maemo be more complete feature wise than MeeGo 1.3 CE?
|
2011-09-29
, 18:20
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#45
|
still think the easiest option would be to pull Meego apart to see how closed source components were implemented, then start from scratch. sounds like a lot but would simplify the task of having to work round on going issues with out of date/closed source apps. would also free project from nokia and make it available for other devices.
The Following 5 Users Say Thank You to mikecomputing For This Useful Post: | ||
|
2011-09-29
, 18:40
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#46
|
And funny is Qml is already faster/smother on MeegoCE than Maemo5. Not sure exaclty why but one reason could be because MeegoCE is using hardfp in GCC.
|
2011-09-29
, 19:11
|
|
Posts: 353 |
Thanked: 166 times |
Joined on Jun 2010
@ India
|
#47
|
|
2011-09-29
, 20:05
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#48
|
The Following User Says Thank You to Android_808 For This Useful Post: | ||
|
2011-09-29
, 20:19
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#49
|
my reason for suggesting a move not centered around meego was based on the fact that the project is transitioning to tizen. Are the current community devs happy with this change? Will the HTML5 focus lose developers? What will happen with QT/QML? Lots of questions whose answers will not be known for some time yet.
Meego, as it currently stands, as several have pointed out, is probably the best way forward at the moment. It is more up to date, better drivers etc etc. My suggestion was purely about in the long term. Unfortunately I wasn't around when Mer was, so I don't know the full story there.
The Following User Says Thank You to danramos For This Useful Post: | ||
|
2011-09-29
, 20:21
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#50
|
my reason for suggesting a move not centered around meego was based on the fact that the project is transitioning to tizen. Are the current community devs happy with this change? Will the HTML5 focus lose developers? What will happen with QT/QML? Lots of questions whose answers will not be known for some time yet.
Tags |
buysomethinelse, winding down |
|
Nokia aren't going to let us have the source for any of the closed components, I doubt this community could raise any amount of money that would interest them, and even it were possible would it be worth it? I want some up to date hardware to go with my up to date OS. I do want to keep my N900 going until someone makes a worthy successor, but until then I think the best route is going the way the CSSU guys are going.