<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Emulation on The IT Hollow</title>
    <link>https://theithollow.com/tags/emulation/</link>
    <description>Recent content in Emulation on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Mar 2012 15:00:21 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/emulation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Virtualization vs Emulation</title>
      <link>https://theithollow.com/2012/03/07/virtualization-vs-emulation/</link>
      <pubDate>Wed, 07 Mar 2012 15:00:21 +0000</pubDate>
      <guid>https://theithollow.com/2012/03/07/virtualization-vs-emulation/</guid>
      <description>&lt;p&gt;Emulation and Virtualization are not the same thing.  In many cases you&amp;rsquo;ll hear them used interchangeably but they are different concepts.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Emulation&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Emulation consists of taking the properties of one system and trying to reproduce it with a different type of system.  When it comes to computers, you may have seen some software emulators that you can install and run on a PC or MAC, that will reproduce the characteristics of an older system such as a Nintendo or other gaming console.  As an example you could then perhaps run Super Mario Bros. on your work desktop (I am not advocating the playing of video games at work).  In this case the software emulator is mimicking the gaming console so that the game could be run inside the emulator, even though the underlying hardware is an x86 architecture.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
