Shortsighted

Rogelio Morrell "How can a product use more XML than the other? XML is XML everywhere you go. But I can understand that InfoPath might be more XML oriented (in that is using XSLT, XPath, etc) than say Word or Excel, because the only save in XML.

Am I wrong or is there anything more?

I definitly think that InfoPath is not for end-users, but I can imagine end-users trying to be developers when InfoPath is release."

I'm going to address this point by point. First off, It's very easy for one product to use more XML than the other. GenX.NET (my ADO.NET exporter) doesn't use any XML at all. Office 2003 uses a bunch. Right there, Office 2003 uses XML more than my app does. And BTW, Office 2003 uses XML WAY more than just letting you save and open to it.

InfoPath is SPECIFICALLY designed for end users, but it will be an outstanding developer tool as well. It allows you to create forms for XML using XSLT and so forth seamlessly, without the end user needing to know what is going on in the background. For the developer, the inner workings are readily accessible, and it will help XML development dramatically.

I'm an Office 2003 beta tester (eagerly awaiting my Beta 2 shipment), so I can't say any more on the subject, except for this: I really hate it when people speculate about things that they don't know anything about or understand. Neither CNET (one of my employers) nor ZDNet understand what InfoPath is yet, so I would hardly take their word as gospel on the subject. My advice to everyone: be patient. MS is STILL trying to figure out how to explain .NET one year later, so you can't hardly expect them to have fully explained their vision about InfoPath yet. Please don't let News.com or ZDNet suck you into their preconclusions before information on the subject is widely available.