Skip to main content

XSLT

I never thought that I would like XSLT and I hoped that I wouldn't have to learn this "wimpy web language" which is how I used to see it. But after this weekend, I am a big XSLT fan.  Which is appropriate because this month marks the 10 year anniversary of XML.

So why is XSLT so cool? I think I would have embraced it much sooner had someone made this simple comparison for me: XSTL is like TSQL. I love TSQL: it is so powerful for getting and manipulating data. It is blazing fast and it takes way way fewer lines of code than it would take in .NET. XSLT is similar because both TSQL and XSTL are declarative languages: they focus on saying what do do rather than how to do it. When writing TSQL or XSLT I only have to say what I want done, and the parsing engine is responsible for figuring out how to do it.

Another way to look at these two languages is that they do one thing really really well: TSQL manipulates data in a database, and XSLT transforms XML.

I strongly recommend the Wrox XML book: Beginning XML. I spent most of my Saturday looking at other XML books, but I always seem to come back to Wrox. They are just so so much better than everything else. Some of the other XML books are just embarrassing and it is a shame that bookstores sell them to poor unsuspecting victims who read them and end up being more confused than when they started reading those horrible books. My advice: stick with Wrox.

<xsl:template match="/">
  <html>
    <body>
      <h3>I love XSLT</h3>
    </body>
  </html>
</xsl:template>

Comments

lu said…
hi mate, you spell beijing wrongly as "bejing" under your picture. nice pic

Popular posts from this blog

How to Create and Run Tableau Bridge on Linux Containers

Tableau Bridge is now availble on Linux Containers. Yay! Now what does this mean and how do I build and run Linux Containers? We will discuss the advantages of running Bridge on Linux Containers the steps to build them, and finally, we will provide some automation script ideas for monitoring and scaling Linux Bridge agents. Tableau Bridge Today Until recently, Tableau Bridge was only available as a Windows application running on a Windows VM. It supported only one bridge agent per Virtual or Physical Machine. Advantages of Bridge in Containers Better Hardware Utilization: Linux containers are more efficient than Windows VMs, requiring only about 1/50th of the disk space. Ability to Spin Up Multiple Bridge Agents: With Linux Containers, it becomes easier to spin up multiple bridge agents on a single machine, improving scalability and resource utilization. Infrastructure Automation: Linux Containers enable easier automation of provisioning bridge agents and upgrading Tableau Bridge, the...

Unleashing Tableau’s Semantic Layer with AI Agents

⚡ TL;DR I helped built a tool that lets you query Tableau’s semantic layer  using natural language and AI. By integrating a LangChain agent with Tableau’s VizQL Data Service (VDS), we can repurpose Tableau’s trusted data model for conversational analytics . This means you can ask questions in plain English and get answers backed by the same definitions and security that your Tableau dashboards use. In this post, I’ll introduce this open-source agentic tool ( tableau_langchain ), why it’s transformative for analytics, and how it works under the hood. Why Connect LangChain Agents to Tableau? As a user of Tableau, I’ve seen how powerful Tableau’s semantic layer is. It encapsulates our organization’s business logic: things like predefined metrics, calculations, data relationships, and even row-level security rules. Traditionally, that semantic layer is only accessible through Tableau’s interface – you drag and drop fields to build a viz, and Tableau generates the query for you. Rece...

RAM Disks do not speed up Visual Studio

  The limiting factor for Visual Studio is disk IO. I got a tip to speed up Visual Studio from Channel 9 by creating a RAM disk which sounded like a great idea. However, when I ran a thorough set of tests, I found that the performance difference between the Ram disk and the hard disk were not appreciably different. This was a big surprise since RAM is 240,000 times faster than disk (see my previous blog post). But the reason is because Visual Studio and Vista do a lot of caching. So compile times for the same project in RAM disk and on hard disk were pretty similar. I also tested the time it took to search the entire solution for a word, and times to open a solution. There was no discernable difference!   If you still want to try it out and create your own RAM disk, you can download a simple RAMDISK.EXE utility to create a RAM disk in just a few minutes. What is a RAM Disk ?   Ramdisk is a virtual drive created in RAM.   Performance Analysis Creating f...