![]() |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
|
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
Hallelujah!!! There is hope.... |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
In a meantime would you reconsider your position to not contribute to CSSU, it is a big loss to this community that such good developers don't contribute. I know for some of you Maemo 5 is dead and developing for it is a waste of time, just hoping not all of you share this belief. |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
|
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
Please do come have a chat anyway - a lot of enlightening things that is afterwards usable in CSSU is often spoken about, such as how things are glued together etc. |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
... but please, don't ask me to distribute working items, I am not a project manager here (not a CSSU team member either). Just a random contributor. |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
see that, there? that was the end falling off the irony meter |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
Quote:
Why are you such a huge liar? Quote:
Quote:
Quote:
Quote:
Quote:
"Hi... MeeGo? Yes, I was told by a person that lies constantly about what I've said, that your origins aren't what you claim them to be on the FAQ on your site. Can you fix that? Thx!" Call me silly: I believe a community FAQ written by the community in question just a smidge more than I do someone who's not involved in the project, and has lied over a dozen times about what I've said already. Quote:
Quote:
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. Silly me, basing my "vague choice of words" on common usage. Quote:
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. But since you're playing these childish word games... Tell me: If there are so many ARM devices, and they're all "virtually identical" as you keep saying they are, why is it MeeGo doesn't work on the N950 and N9? I mean, really... if it all translates so well, and every pocket calculator is a suitable testing system, it should just work on the N950 and N9, shouldn't it? 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. You need things to be very close, especially as the complexity of the system goes up. The oven timer software may very well run on my calculator. MeeGo will not. They all run ARM processors... Quote:
A frog in a pot of water will eventually die. A frog in a pot of boiling water will die much faster. Quote:
Thanks again for proving my point. Again. Quote:
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. Quote:
Quote:
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. Quote:
Quote:
I'm not debating if is should or shouldn't have. I'm talking about the factual past. The N900 was not targeted at the generic public. It was targeted, quite specifically, at a very narrow crowd. This whole vein is off point though... you're good at that if nothing else: Squabbling about semantics and veering off topic when you're proven wrong, and/or have no facts to back up what you're saying. Quote:
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. Which of those two ideas do you think will attract more developers for your new system? One where someone has to spend hundreds of dollars on an otherwise useless prototype system and then work to get it barely working? Or one where they already have a compatible system in their pocket, at 70% functionality? Quote:
Quote:
Quote:
Tell you what... Let's just see... In a year or two, I'm betting MeeGo is about as used as ofono is today (eg, not much). I'm also betting Maemo will still be the OS of choice on most N900s that are left, because the MeeGo CE project is dropped by Nokia and left behind, like Win 3.11 was when Win 95 came out. Time will tell. |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
/me rubs hands together... Sorry folks, but I'm really having a good time doing this.
Maybe we could move this thread to offtopic so that it does not spam the Active Topics list? After all, all that could be said about the original thread question has been already said in post #3. Quote:
Quote:
How are you going to avoid posting a retraction this time? Quote:
Quote:
Quote:
I'm sure you'll excuse if I laugh all the way down about this. You surely must know there's a large difference between microcode+renaming (like in the Pentium Pro, NOT the Pentium) and emulation (like the Crusoe). Saying the Scorpion "emulates" the ARM ISA is just laughable, for many reasons. It _IMPLEMENTS_ it. If you read about any of the previous examples you'll know the difference. Quote:
Quote:
Quote:
Quote:
This also reminds me of your weird assertions about the x86 architecture that are against both common usage and technical usage. Quote:
Quote:
Quote:
Quote:
Quote:
Classic. Quote:
Quote:
Quote:
What the heck does "Using an open wifi point and requiring ssh routing to get past the router" mean? "SSH routing" is one confusing term.... Quote:
Quote:
Quote:
Quote:
Quote:
_You_ started the talk about market segments. By saying the N8x0 and N900 where in different ones. |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Holy **** I can't read all of this!
Smaller words and less of them! |
All times are GMT. The time now is 09:04. |
vBulletin® Version 3.8.8