Geek Answers Handbook

Current state of client XSLT

Recently, I have heard that Blizzard was one of the few companies that has implemented XSLT on the client side (2008). Is this still the case in 2011, or are more people now learning this technique in production?

It seems that modern browsers (IE9, FF4, Chrome) and processing power of client applications are used to use this standard for tangible power savings and CPU bandwidth on a large scale. Did I miss something?

The negative aspects that I know of include

  • extra rendering time
  • additional resources required to download without page loading
  • extra difficulty
  • significantly less developer experience than server-side template methods.

The benefits that I perceive include

  • composition of the template uploaded to the client
  • caching common template fragments uploaded on the client
  • logical separation of document structure and data
  • well-documented web standard supported by all modern browsers

Finally, although I know that it is impossible to predict the future, I am curious to know opinions about whether the client XSLT day will come. With an interest in HTML5, forcing users to update their browsers and developers to learn new technologies, I really want to see what is developing.

Thanks in advance,

Casey

Edit:

Any understanding of how converted XML is viewed by Google, and the implications it has for SEO, are also appreciated.

+8
html xml xslt
source share
6 answers

I may somehow get lost in the translation, but I think that SEO problems are the main reason preventing many people from using XSLT client.

I don’t know the search robots that can analyze the application / xml instead of simple html or even flash.

However, this is a good practice (in fact, mail.yandex.ru is a great example) for highly loaded web applications to use XSLT partially on the client, because the traffic is large and SEO friendliness is not required.

+2
source share

I am using client XSLT on kulesh.info . I did not find the differences in IE 6-9, Chrome, Safari, and Firefox. XSLT conversion is very fast. I haven’t taken any speed measurements, but I don’t see any difference compared to the pure HTML version (even on the first generation iPod Touch).

mail.yandex.ru (a large mail provider in Russia) also uses XSLT on the client side.

+3
source share

Recently, I heard that Blizzard was one of several companies that placed the XSLT client in practice (2008). Is this still the case in 2011, or are more people now learning this technique in production?

Here are some examples:

Some people claim that XSLT is not intended to be "programming in general" - for example, it does not have any separate compilation capabilities. Hopefully, the upcoming XSLT 3.0 will change that.

+3
source share

The problem with XSLT material on the Internet is that there are many other things that can be used instead that are easier for developers. I never see XSLT stick to the Internet in the form you describe, in fact I believe that Blizzard actually pulled client-side XSLT transfers from their sites when they recently made some redesigns to consolidate their brands.

Believe me, although I would like to, I wrote a solution for a company in which I worked in the past that used XSLT translations for all of its templates. He did not use client-side translations, because it was in 2005, when there was still a large market share of browsers that did not support client XSLT. One of the biggest problems we had with this system was to find developers who could help with this. And when you found someone who could work with him, they would crush a lot of templates, because XSLT development is a different beast than any other template language.

While the benefits of using XSLT are huge (do a google search for symphony, a great cms that xslt uses as it uses templating). I do not see this significantly strengthened for interface development.

+2
source share

When deciding whether to use XSLT, this usually comes down to the cost of developer time and the expected benefits in the CPU cycle. For a small client, this almost universally means: XSLT, if it exists, goes on the server side. For clarification of all problems of the client simply not enough benefits.

If a breakthrough occurs, it will be on large sites such as facebook or google. On these processors, the cycles uploaded to the client will amount to a significant $$$, sufficient to justify hiring developers (developers) who will alleviate problems with the client. I would watch these players to see if a change will occur.

+1
source share

I made an XML-XSLT website a couple of years ago for a project in school and noticed an error: Firefox does not support disabling I / O.

https://bugzilla.mozilla.org/show_bug.cgi?id=98168

+1
source share

Source: https://habr.com/ru/post/650681/

More articles:


All Articles