![]() |
2011-09-06
, 18:18
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#242
|
It's FUD. There are few if any hardware devices planned for i386 either, so that would mean Meego doesn't target x86!
No. The FUD is saying "the N900 is a device it was never intented to work with".
![]() |
2011-09-06
, 19:01
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#243
|
And if we look at the hard data without "maemo is dead" glasses we may conclude that peak values in the first months after n900 launch are because of bugfixing builds, can we?
Because bringing application into extras is not so easy task, that is why one needs several iterations devel->testing->bugfixing and again from the begining.
We may also conclude that after an year and a half developers are much more experienced with the platform, have development tools (Qt,qml) in their hands which were not available in the begining, etc. which shortens development and reduces number of iterations needed to make an application stable.
The Following User Says Thank You to javispedro For This Useful Post: | ||
![]() |
2011-09-06
, 19:24
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#244
|
You're on crack. It targets x86 for the same reason Maemo does: emulation and debugging.
So let me ask this again. What other ARM based devices are planned to run MeeGo? 0. None. Zip.
And since there aren't millions of ARM based PCs that people are going to use to debug their code on, ARM has a limited life cycle on MeeGo once non-ARM devices are introduced.
Right now, it's there for N900/N950/N9. But once the N9 hits the market, N900 specific hacks will be less and less supported. And once the N9 is gone and Intel based systems are out, ARM support will go away even more.
The only way that's going to change is if more ARM based devices become available running MeeGo. That could happen, in which case we're in luck. But none have been announced yet beyond the N9 (by any company, not just Nokia). Please do correct me if I'm wrong.
I never said MeeGo wasn't intended to run on the N900. I said the N900 was never designed with the intent that it would run MeeGo. You're calling fud on me say X was not intended for Y, when what I said was Y was not intended for X. Maybe if you read what people are writing instead of just screaming "FUD" all the time you wouldn't make such simple mis-interpretations.
And lets be clear here. MeeGo added support for the N900 early because it was the only device that met the criteria for it's design purposes.
Again, I'm not talking about how many projects there are, or how many more developers there were for X vs Y. I talking about pure and simple numbers here. There are more N900s out there, and the hardware (minus the USB port) is robust enough and modern enough that it's not being outdated as quickly as it's ancestors.
You're comparing apples and amigas. They're not the same.
Again, you're totally allowed to think that. I, personally, do not think MeegoCE is going to ever get to the point that it can do what Maemo did from the day it shipped, yet alone what it can do now. And if it can't do that, it's not going to prevent the demise of the device any more than iOS updating is going to help it. If it makes it to something even close to feature parity with PR1.0 (or better), then I may change my tune. But right now, where I see it going, it's not going to make it. I'd love to be proven wrong... I really would. But I just don't think it's going to happen.
![]() |
2011-09-06
, 21:57
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#245
|
It was you the one who was FUDing saying Meego's main target is x86!
So what? Are there any devices planned to run Maemo, other than the N9?
It seems stupid to me that you are arguing that ARM devices are scarce.
My main point in this argument has always been that the fact that these hacks (closed blobs, etc.) are present in a much more reduced number in the MeegoCE for the N900, it will be MUCH easier to keep those supported.
The Maemo ones are already dead. How many times will I have to repeat this?
I don't understand how you were able to, on a single paragraph, both mention "the release of the N9 is going to hurt Meego for the N900" and "the release of the N9 is the going to help".
You're going to also say there were conditional statements on this one? MeegoCE has _obviously_ been promised to work on the N900.
I don't know, wouldn't that be because Nokia paid for it to happen? I'm just completely surprised how can you ignore this documented fact and instead go on and reinvent history.
Ah, another N900centrism. You all sept2009ers could try and be a little less N900 centric, really.
I do not think MeegoCE is going to get to the point that it can do what Maemo did from the day it shipped either.That's not changing my predictions though. .
The Following 2 Users Say Thank You to woody14619 For This Useful Post: | ||
![]() |
2011-09-06
, 22:23
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#246
|
The thing is, most people don't see ARM based computers as "computers".
I can still talk to wifi devices. I can still use bluetooth. I can still make GSM calls. Maemo binary blobs won't stop working because some new update in the core software causes an incompatibility.
With the N9 coming out, development will shift to it, and away from the N900. That means fewer people working on the N900, which means fewer people fixing and tweaking (or caring about) the N900.
By whom? Nokia has never promised it. MeeGo has never promised it. MeeGo CE has never promised that MeeGo would ever be "productised" or ready for the average N900 user.
Tell me: When the N900 was announced, how much work happened on Diablo on Nokias part after that date?
![]() |
2011-09-07
, 02:20
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#247
|
So, you didn't knew that Meego had an x86 target.... but you did know there was a Atom device in the pipeline?
So you say there are no Meego ARM devices in the pipeline, but you did know there is a Snapdragon in the pipeline? Well, Snapdragon is ARM.
Well, MeegoCE is designed for ARM. What other architecture could it be designed for?
According to Intel, MeeGo was developed because Microsoft did not offer comprehensive Windows 7 support for the Atom processor.
I am going to tell you of a few devices on the Meego pipeline: the N900. The N950. And the N9. And I don't mean Harmattan.
So you now think that most people don't see ARM devices as computers.
So you think the only device that has "GSM, wifi, a keyboard, touch screen, Gigs of space, reasonable ram, and a fast core with an open bootloader" is the N900. More stupidy.
...
Even the Beagleboard made it.
But more important, why wouldn't they _use_ the N900? Nokia paid for it.
So you think your closed blobs won't stop working. I hope you know that Google is currently implementing a special workaround in their servers for N900 video call support.
You also fail to understand something. If you use a product way past its official support time, you no longer are "average user".
You are here. MeegoCE project is targeting you. Take that as hint and contribute.
Little. But please note that MeegoCE is _already_ a larger effort from Nokia to release updated stuff for a past device than the previous attemps (HE editions) were.
And the fact that you don't even want to compare to the N8x0 (same forum, virtually same device & software, same company behind it, virtually same employees, virtually same userbase) should make you rethink the facts twice at least.
I'm getting tired of your complete _horrible_ mistakes about the history and the facts of Meego, like "no real support for MeeGo on ARM until Nokia joined the party" (how could that be if NOKIA IS THE DAMN FOUNDER OF MEEGO!!!!!!!!!),
What specific features of Moblin and Maemo are being used in MeeGo?
MeeGo blends the best of Moblin with the best of Maemo, to create a platform for multiple processor architectures covering the broadest range of device segments. MeeGo builds upon the capabilities of Moblin core software platform and reference user experiences, adding the Qt UI toolkit from Maemo.
that when I rebuff you start saying that "I meant to say" or "you should have understood that".
If you want to keep this flamewar, please Google a bit before posting.
![]() |
2011-09-07
, 03:15
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#248
|
You do if you want anyone to take your point of view seriously.
Sorry, but if you're not willing to explain your point of view, you deserve to not have people bother listening to you. If you can't be bothered to explain yourself, I can't be bothered to listen to you.
And telling others to "go read my posts" for that information is both childish and, in your case, misleading. I've read most of your posts, and frankly you've never tried to explain anything you've said or done. So there's no place to "go read" that does what you're saying.
Man up... Explain your reasons for your viewpoints. If nothing else it will help you clarify your own views, and give others insight on how you come to conclusions.
![]() |
2011-09-07
, 04:21
|
|
Posts: 434 |
Thanked: 990 times |
Joined on May 2010
@ Australia
|
#249
|
![]() |
2011-09-07
, 06:27
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#250
|
![]() |
Tags |
context, debate, developers, frappadecaf, infraction pts, javis vs. woody, let's troll!, meego, relevance |
|
Sorry, but if you're not willing to explain your point of view, you deserve to not have people bother listening to you. If you can't be bothered to explain yourself, I can't be bothered to listen to you.
And telling others to "go read my posts" for that information is both childish and, in your case, misleading. I've read most of your posts, and frankly you've never tried to explain anything you've said or done. So there's no place to "go read" that does what you're saying.
Man up... Explain your reasons for your viewpoints. If nothing else it will help you clarify your own views, and give others insight on how you come to conclusions.