XQuery as a general data processing language WAS:
[xquery-talk]XQuery and Web 2.0
pc.subscriptions at gmail.com
Sat Apr 26 13:45:20 PDT 2008
I honestly do not care about which language I am using and even less
under which buzzword of the day that language is classified and I am
certainly in favor of reducing implementation time of the applications
we are trying to build (and I have the luxury of being able to make a
If XQuery or XSLT can do that for me I yet have to figure out how that
would work. It certainly brings a lot, but it just does not cover all
the needs. Once I have to integrate what they bring in what I am using
for the rest of the app I tend to loose as much time as I have gained.
Very eager to learn how that would work indeed - believe me I would
enjoy my job more if I could do more XQuery and less DOM or XQJ
Guidance or pointers more than welcome!
On 26 Apr 2008, at 09:37, Michael Kay wrote:
>> Well...ok....what about something like a non proprietary LINQ
>> done properly?
> Using terminology that has gone out of vogue, XSLT and XQuery are
> fourth-generation languages, LINQ is a third generation language
> with 4G
> add-ons. I'm a great believer in using 4GLs for writing business
> applications, I've been doing it since the 1980s and I believe the
> productivity and maintainability benefits are immense. You should
> never let
> your business data anywhere near Java unless you are doing something
> substantial algorithmic complexity, like traffic scheduling. Every
> time I
> see people doing it, I see a team taking months to implement new
> when it should take days.
> Michael Kay
More information about the talk