|
Joe,On the other hand, IIRC Powerpoint was Microsoft's baby. And I love that tool. I'm also a big Publisher fan; there's no open source equivalent that I've been able to find.
I don't think you're mud-slinging at all.
This wouldn't be the first time; Microsoft is very good atassimilating other technologies.
Agreed 100%. Although I would like to know who they assimilated
"Microsoft Bob" from. :) Or maybe that was an original, it would explain
a lot.
However, you've failed to address the main thrust of my last email. IsThat's why I suggest you send some email to Blair. I'm not privy to the underpinnings. My guess, though, is that this code base differentiation was part of the reason behind the introduction of the standard JVM into the i mix. I get a little confused here; the classic 64-bit JVM is i-specific, but the 32-bit JVM is consistent across i and p.
much of this great IBM system code implemented on i? Seriously? The
latest link to one of Toshio's articles, refers specifically to
optimizations on IA-32, which I think we can both agree is not the
underlying architecture for i. :) This wouldn't be the first time IBM
had lots of cool stuff, but it wasn't available on i, because i "is
different". :) Look no further than DB2 and ContentManager for two
examples of places where what's on i and what's on other platforms may
share a product name, but don't share code.
Especially after sitting through a couple sessions at NEUGC earlier thisI'm not saying anything like that. Because I really wasn't doing i vs. .Net, at most I was doing IBM vs. Microsoft and maybe Java vs. .Net. My sole point was that JIT is nothing new. I'd be interested myself to know how much of the IA-32 work translates to the Power architecture.
week, I don't accept "it's in there", "we just do it", and "you don't
need to worry about that" as answers for stuff on i.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.