My contention wasn't that it was the same amount, but that the items that are closed in both will cause both to meet their demise at about the same time. So, no... not "proven false".
I'm saying when comparing two systems that are almost identical in which parts are closed vs open (in this case Maemo and MeeGo CE for N900, which is the only part of MeeGo we've been talking about in this thread), it makes little difference if one is marginally more open.
Again, why would you build something not useable? No... I said that the goal of MeeGo CE was to make an OS for developers, not for every-day N900 users.
MeeGos main target (having started with Moblin) was Atom, not ARM. ARM was added as it was transitioned. So no, that was proven TRUE, not false, despite your objections to reality.
I know damn well what microcode is. The point being, AMD has never made an x86 line, nor have any of them be "x86". You saying it has is laughable, or pitiful, I'm not sure which.
I never said you did. Read wtf I'm writing. I said just having a target doesn't mean you can run the whole system on a platform designed around that target. You've implied that because the upstream kernel supported a compile option for ARM that MeeGo (or Moblin, or anything using that kernel) somehow magically works on the target, which is FALSE. In order for the whole system to work, it must all be ready to run on that platform, including drivers, libraries and middle-ware layers. Moblin was not capable of running on ARM because of that, and neither was MeeGo at it's conception, until Nokia rolled in it's changes.
The implication you made was that it was contributed by Nokia alone to a new project by Intel and Nokia. Reality is that Intel already had ofono, as it was a joint development. That would be two people buying a gift for themselves, then later opening it with people around, and you going "that one gave that gift to the other". No... ofono was a joint effort. MeeGo was a joint effort, by the same two companies. Nokia didn't bring ofono.
And to say Nokia doesn't contribute to Meego other than the Qt GUI... look at sensord, ofono, even the kernel...
If I show said calculator to anyone without a degree in CS (and most people with one) and ask "what is this?" the answer will not be "a computer". It will be "a calculator". If I then ask "is it a computer?" most would still say no. In a strict sense, an abacus in a computer, since you can do computation on it. But that's not how the term is commonly used. This is all beside the point though.
What I said, had you bothered to read the post, was that there weren't enough ARM PCs with the correct level of hardware features commonly available. I even made a bullet pointed list of the requirements. You'll note that among them were things that even the latest BeagleBoard doesn't come with, like a GSM module, and a display.
why is it MeeGo doesn't work on the N950 and N9?
And if they're "virtually the same hardware" as you've said many times now, what's the hold up? It's the same! You should be able to run it on the N8x0 and N7x00 as well, right?! They're virtually the same as a Beagle Board. You said so!
No... MeeGo can't. Because your logic is wrong... It's not a simple translation for one to the other.
Yes, new sub-platform development is more MeeGo developmet, but the inverse is not true. More MeeGo CE like projects means LESS work on MeeGo CE, as people migrate to better platforms, and have limits on time. More MeeGo development also means more chance that the core will move on, causing old blobs to be incompatible. That will either cause CE to either need huge divergent changes to keep up, or to freeze once those binary blobs are no longer updating.
No.. not wrongly. Again: If the Beagle Board is so good, why is Meego not running on the N950 or N9 yet? Why can't it run on those if the Beagle Board is such a suitable test platform. The answer is, it's can't because it's not.
Also, again: There would be far less interest (and far fewer people working on it) if one had to go out and spend hundreds of dollars on an otherwise useless kit just to join in.
That's great... And how does that help AT&T turns on the TMobile 3G frequencies? Oh, wait... it doesn't. The example about wifi I gave wasn't to talk about blobs. It was to talk about the fact that there are still methods to use hardware sometimes even when you can't upgrade it to the latest technology. For example, using an open wifi point and requiring ssh routing to get past the router. But that's not useful when the changes are locked into hardware. The N900 faces just such an issue around 3G. MeeGo can't fix that, even if it goes 100% opensource.
Except that I mentioned it directly after the quote you cut, where I said "there was a commercial made, though I'm not sure it ever made it to anything but YouTube." Thanks for posting the link to the one example I gave as the exception, on YouTube.
Again, as far as I've seen, that advert was never played on any commercial station. There was not a second if air time purchased by Nokia for advertisement of the N900 in the US, and very little elsewhere, very similar to the campaign for the N9.
Yes, Nokia can. Can you? Can the average developer? Maybe everyone developing for MeeGo could just go out and buy a multi-hundred dollar Beagle Board, on a whim, so that they can participate in Nokia/Intels new OS?
Or, here's a crazy idea: Nokia can spend a little bit on a small core of people to back-port the new OS to a platform that lots of developers already bought, and are carrying around in the their pocket right now! Imagine that! They can develop for it without having to purchases a multi-hundred dollar kit that serves no other purpose than to tinker on.
Who's talking about market segment? You said the N810 wasn't a tablet. Just like I said that everything with an ARM processor in it isn't a "computer". Why do you have such a stick up you posterior about calling an oven timer a computer, but then don't want to call something the the word tablet in it's production title a tablet?