<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Responsible Artificial Intelligence LLC</title>
    <link>https://responsibleai.tech/posts/</link>
    <description>Recent content in Posts on Responsible Artificial Intelligence LLC</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Jan 2023 15:00:00 -0500</lastBuildDate><atom:link href="https://responsibleai.tech/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running Windows on Apple Silicon</title>
      <link>https://responsibleai.tech/posts/2023-01-27-utm/</link>
      <pubDate>Fri, 27 Jan 2023 14:58:53 -0500</pubDate>
      
      <guid>https://responsibleai.tech/posts/2023-01-27-utm/</guid>
      <description>
        If are a developer who recently got a Mac with Apple Silicon, one of the unexpected pain points you might have is that your toolchain around containers and virtualization could break. As explained in a Gingko Bioworks blog post, macOS and Docker support for emulating 64-bit Intel (x86_64 or x64) at the instruction level has improved since the launch of the first M1 chips in mid-2020, but you can occasionally can into low-level compatibility issues where such low-level emulation fails.
      </description>
      <enclosure>https://responsibleai.tech/posts/2023-01-27-utm-screenshot.png</enclosure>
    </item>
    
  </channel>
</rss>
