Node.js interest and adoption have reached noteworthy levels among enterprise customers.
Architectural design of solution systems is simplified when a new platform (Java or .NET) needn't be introduced just for XML technology.
As an aficionado of functional, declarative, and rule-based paradigms, I would love to develop for my clients in Lisp or any number of non-imperative languages that are unfortunately permanently niche-bound now. Similarly, I see technical merit to Saxonica's Saxon-CE and (current) Saxon-JS design decisions in the browser. However, socially it is simply not happening: General UIs are not being written in XSLT in the browser and never will be to any significant extent in production settings.
Work is offloaded from central servers, reducing performance bottlenecks and processing costs.
Sensitive data need never leave customer premises.
Network bandwidth usage is reduced when the size of the data being transformed greatly exceeds the size of the XSLT code and libraries (yes, including parsing and serializing components).
Updated by Michael Kay about 6 years ago
We also recognize the use case for a client-side configuration in which the event-handling extensions are disabled.
Please register to edit this issue