What is XQuery doing wrong and why does it get ignored !?

[Daniela Florescu]

Good morning, too,

>>
>> We are going back to O'Reilly. Please don't confuse eyeballs with  
>> business value.
>
> But you continue to make arguments that do exactly that. You're  
> bemoaning the lack of *popularity* of XQuery throughout this thread  
> but then try and switch to "business value" to attempt to justify  
> the "XQuery is so much better and people just need to realize and  
> then everybody will be happy and get a pony" -- that's exactly kind  
> of thing that the Lisp fanatics died from. You can't have it both  
> ways (but since that's a personal belief issue, I'll shut up about  
> this now).

John, I am afraid we are talking pass each other.

What I was complaining is that opinions of the kind "Nobody's using  
XMl in financial world" or "everybody uses JSON"
are prevalent in the Web 2.0 crowdish. That's just folklore that has  
to go away, because false.

I never supported XQuery becoming a language to write network  
protocols or operating systems in.

But if I have an enterprise information-driven application, that  
processes invoices, generates spreadsheets
from it, sumcounts, and finally prints pdf letters from it, yes, in  
this case I  don't know of any other technology that
does that better/cheaper/faster then XQuery. Just an example.

And no, Lisp has never had a "business value".

But I (and not only me) CAN clearly articulate the impact that using a  
information  streamlining processing methodology
can have on your business.

Cut costs, increases control by extra available information, gets you  
faster to market, and allows you to adapt quicker to changes.

> " XQuery is so much better and people just need to realize and then  
> everybody will be happy and get a pony"

Some people already got their pony. Just ask MarkLogic consultants :-)

A bon entendeur, salut.

Best regards
Dana