Re: XSLT vs Web Components

Well, one that I worked with was ICL QuickBuild, which was used by a few
hundred mainframe users in the UK for generating transaction processing
applications (some of them massive applications). It actually had many
XSLT-like characteristics (which is what attracted me to XSLT when I first
encountered it). A program was a declarative description of an entire user
session, with all the management of session state taken care of behind the
scenes. There were quite a few such languages - most, like this one, tied to
particular hardware and software environments. Software AG's NATURAL is
another example. I don't think any 4GL had more than about 3% of the market,
and that's mainly what killed them - no standards, no critical mass.

Michael Kay
Saxonica
mike@xxxxxxxxxxxx
+44 (0) 118 946 5893




On 11 Sep 2014, at 16:55, Ihe Onwuka ihe.onwuka@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Thu, Sep 11, 2014 at 4:20 PM, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> I would like to think that the only thing that will lead to XSLT's decline
is when someone invents something better, and there's no sign of that on the
horizon. This might be wishful thinking, however; there were some excellent
special-purpose languages in the 1980s that didn't survive because they didn't
have a viable user and developer community, despite being ideally suited to
their task
>
> Like for example?
>
>
>
> XSL-List info and archive
> EasyUnsubscribe (by email)