Replies to post #91823 on Intel Corp (INTC)

[fastpathguru]

So I guess we're in complete agreement... Including my original assertion that the "x86 codebase advantage" is not a factor in the Meego/Android argument, even for the x86 architecture.

No, you're still saying the same thing for the same wrong reasons.

Code base != binaries. Code is for example C++, and that can and will certainly be leveraged for Meego/Android ports, with good tools to assist ISVs in the process.

The traditional "x86 codebase advantage" argument IS re: binaries, I.e. my old apps will simply run on my newest PC.

Re: your interpretation of the codebase argument (i.e. codebase is source, not binaries): This "Intel toolchain & support that prefers x86" is, so far, all in your head and unsubstantiated; Meego is EXPLICITLY CHARTERED to be a common development platform. Cross-architecture. Android even more so.

You seem to be saying that Intel is going to introduce a to-be de-facto "standard" Meego platform (with special toolchain support) that, while supposedly feature complete (otherwise it would be non-competitive), it will be either difficult or impossible to port applications from it to an ARM-based Meego device.

A) I really don't think you understand Meego's raison d'etre:

http://meego.com/about

(Does that look like a platform about to fork off an incompatible x86 version?)

B) Show me exactly where these "tools" are. Or something that shows that they're coming.

I think you're just arguing about a possibility (I don't dispute what you're saying is possible), while I'm arguing about the reality.

fpg