<pre><code>&#x3C;h2 class="text-2xl font-bold mb-3">Flashback to Flash: My Thoughts from 2003&#x3C;/h2>
&#x3C;p class="text-base mb-4">In March 2003, I was quoted in an article about the controversial redesign of Macromedia's website. This redesign drew significant criticism largely because it relied heavily on Flash, which wasn't compatible with several browsers at the time, including Apple's Safari.&#x3C;/p>

 &#x3C;img class="w-full my-4" src="/assets/images/cnet-flash.png" />

&#x3C;a href="https://web.archive.org/web/20030401172716/http://news.com.com/2100-1046-991868.html" class="underline text-pink-500 text-base my-4">https://web.archive.org/web/20030401172716/http://news.com.com/2100-1046-991868.html&#x3C;/a>

&#x3C;h3 class="text-xl font-semibold my-2">The Issue with Flash and Browser Compatibility&#x3C;/h3>
&#x3C;p class="text-base mb-4">The article, titled &#x3C;em>"Revamped Macromedia site irks customers"&#x3C;/em>, discussed how Macromedia's decision to build their site entirely in Flash alienated many users. Not only did this choice lock out users of browsers like Safari and Opera, but it also raised questions about the usability and accessibility of web content. At the time, I commented:&#x3C;/p>
&#x3C;blockquote class="border-l-4 border-gray-500 pl-4 italic mb-4">"I definitely believe that Macromedia is alienating their core developer superstars with their latest Web site offering. It is too slow, a bandwidth hog, and doesn't work with a browser that many of these Flash developer superstars are using. Whether this is 'a lot' of people I'm not sure, but surely they are the alpha developers that so many of us read and trust."&#x3C;/blockquote>

&#x3C;h3 class="text-xl font-semibold mb-2">Reflecting on the Web Then and Now&#x3C;/h3>
&#x3C;p class="text-base mb-4">It's fascinating to look back at how web development has evolved since then. Flash, once a cornerstone of dynamic web content, has been retired, largely due to its limitations in performance, accessibility, and security. The web has moved towards more open, standards-based technologies that ensure greater accessibility and functionality across all devices and browsers.&#x3C;/p>

&#x3C;h3 class="text-xl font-semibold mb-2">Why It Matters&#x3C;/h3>
&#x3C;p class="text-base mb-4">The story from 2003 serves as a reminder of the importance of forward-thinking in technology. We must consider how our decisions affect a diverse range of users, including those with disabilities. Accessibility and compatibility should be at the forefront of web design, not an afterthought.&#x3C;/p>
&#x3C;p class="text-base mb-4">This journey through a past article is not just about reminiscing but also about learning from the past as we continue to build more inclusive and functional digital experiences.&#x3C;/p>
&#x3C;p class="italic text-base">Flash might be gone, but the lessons remain as relevant as ever.&#x3C;/p>
</code></pre>


Discovering an old quote of mine in a 2003 article discussing Macromedia's website redesign, highlighting the challenges of web accessibility and browser compatibility in the era of Flash.

Browser Compatibility

Remember Flash?