@zachleat Haha, well… beyond that one use-case, do you feel XSLT brings value to real production use cases?
Posts
-
If your JavaScript framework doesn’t support web components, it doesn’t support the web platform. -
If your JavaScript framework doesn’t support web components, it doesn’t support the web platform.@zachleat Exactly. And I think we’ll see whether web components are going to feel stale like XSLT in >10 years.
-
If your JavaScript framework doesn’t support web components, it doesn’t support the web platform.@zachleat I’ve had my share of experience with XSLT as well. I liked XQuery better, but that never made it into browsers. Anyway, my point was more that just because something is built into all browsers doesn’t necessarily mean it’s a good idea to use it.
-
If your JavaScript framework doesn’t support web components, it doesn’t support the web platform.@zachleat Strong “If your web framework doesn’t support XHTML and XSLT, it doesn’t support the web platform” vibes here.
I’m usually all for using web-native tech without intermediary tools. But that’s because it brings me benefits like easier debuggability, better performance, more control, etc. As much as I’d like to say that of web components unfortunately I can’t…