size of XQuery developer community

[Daniela Florescu]

>  it will always be a marginal language (for example, that's how I  
> see the XQ scripting in the browser situation; it's simply not THAT  
> much better than JavaScript, and has the disadvantage of not having  
> a million libraries and code snippets and programmers).


XQuery in the broswer's advantage is not the fact that you write  
better code then in Javascript
(I agree, good enough is good enough, and javascript is good enough).

The major advantage of XQuery in the browser is the fact that you can  
do data and query shipping from the
  server to the browser and back. The fact that you don't need to  
write the processing twice : once in Java when
you want it to run  it on the App server, and once in Javascript when  
you want to run it in the client.

Same XML data can be used on both sides, and same XQuery code can run  
on server and client, and you can decide
what to run where LATER.

That's a major problem with existing applications servers today: they  
cannot run in disconnected mode. You cannot take
your relational data and SQL server with you, plus the app server and  
download them on your laptop before you take a plane.

You CAN do that with XML and XQuery.

Best regards
Dana