VOEvent session

[Frederic V. Hessman]

Alasdair,

In the "real" world, I believe to have heard that Ruby has replaced  
Perl and Python.  And I believe to have also heard that Java is  
effectively dead and isn't being used by anyone for "serious" work.   
When I was young, one knew that the future was Lisp.

As far as JSON is concerned: one woman's <> is another man's {}.   If  
you want simplicity: we could all agree to use Windows *.INI registry  
file syntax and be done with it.

Complexity isn't a question of whether one uses <> or {} or whether  
tags have attributes: complexity is simply complex and any hopes that  
inherent complexity will suddenly turn into inherent simplicity are  
bound to be dashed (which is not to say that inherent simplicity can't  
be expressed in needless complexity, but VOEvent 2.0 is not about  
inherent simplicity).

Rick

>
> Rick Hessman wrote:
>> While this discourse is reasonably entertaining, I keep forgetting  
>> the point.....
>>
>> Here are some theses I'd like to tack onto your virtual church doors:
>>
>> * XML is here and probably to stay and there's nothing reasonably  
>> useful to replace it (yet).
>
> XML, SOAP and the entire WS-* stack and associated complexity has  
> more-or-less proved to be a dead end. In the real-world it has long  
> (a couple of years?) been replaced by RESTful architectures using  
> JSON for transport.
>
> For new development here at Exeter I've entirely switched to JSON  
> based transports for various kinds, either RESTful calls or JSON-RPC  
> when needed. I've more or less abandoned XML-based services,and am  
> gradually reworking code to drop support for XML where practical.
>
> As always however, YMMV.
>
> Al.