<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Amd on David Calhoun's blog</title><link>https://www.davidbcalhoun.com/tags/amd/</link><description>Recent content in Amd on David Calhoun's blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Apr 2014 11:59:21 -0700</lastBuildDate><atom:link href="https://www.davidbcalhoun.com/tags/amd/index.xml" rel="self" type="application/rss+xml"/><item><title>What is AMD, CommonJS, and UMD?</title><link>https://www.davidbcalhoun.com/2014/what-is-amd-commonjs-and-umd/</link><pubDate>Wed, 30 Apr 2014 11:59:21 -0700</pubDate><guid>https://www.davidbcalhoun.com/2014/what-is-amd-commonjs-and-umd/</guid><description>&lt;h2 id="-warning-this-is-an-old-article-and-may-include-information-thats-out-of-date-">⚠️ Warning: this is an old article and may include information that&amp;rsquo;s out of date. ⚠️&lt;/h2>
&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>Over the years there&amp;rsquo;s been a steadily increasing ecosystem of JavaScript components to choose from. The sheer amount of choices is fantastic, but this also infamously presents a difficulty when components are mixed-and-matched. And it doesn&amp;rsquo;t take too long for budding developers to find out that not all components are built to play nicely together.&lt;/p></description></item></channel></rss>