[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] XSLT vs Web Components

Subject: Re: [xsl] XSLT vs Web Components
From: "Mark Giffin m1879@xxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Sep 2014 20:35:22 -0000

On 9/11/14 7:46 AM, Matthew L. Avizinis matt@xxxxxxxxx wrote:
> One of the primary uses of XSLT is transforming xml to html, it seems 
> like.  I don't have data handy, but based on what I've read on this 
> list over the past dozen years or so, seems like a reasonable enough 
> conclusion.
> I've recently been reading about X-Tags, Polyfil, Web Components, 
> etc., and tinkering with it. (for instance, x-tags.org, 
> webcomponents.org, and 
> https://developer.mozilla.org/en-US/Apps/Tools_and_frameworks/x-tags).
> It seems like pretty cool stuff and it occurs to me that by using it 
> one could pretty much eliminate the use of xslt for such 
> transformation, if I understand it correctly.
I can see a lot of uses for them, but I'm having trouble imagining how 
web components would eliminate the use of XSLT. Can you explain more 
what you mean? They are not presented as a transformation language. 
They're actually presented as a browser-native way to do UI widgets that 
are easy to share and use for web apps.

> 1) Do you think the web components concept will catch on widely?
Yes most likely in my opinion.
>   2) will they be supported by browser developers natively eventually, 
> do you suppose?
They already are supported in Google Chrome and Firefox Nightly (you 
have to enable a flag). You don't need polyfills in these two browsers 
that I have seen after working with them a bit.

Mark Giffin

Current Thread