<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #qemm</title>
    <link>/tags/qemm/</link>
    <description>Recent bookmarks tagged #qemm</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:59 +0000</lastBuildDate>
    <item>
      <title>Google Chrome-Induced Déjà Vu - GigaOM</title>
      <link>http://gigaom.com/2008/09/03/chrome-induced-deja-vu</link>
      <description>&#34;Reading the Google Chrome comic strip made clear the parallel to the emergence of QEMM and DESQview: All today’s browsers are effectively single tasking, in that only one tab can be actively processing, say, a JavaScript application at any given time (”inherently single threaded”), yet the tabs are interactive to the point where the misbehavior of an “application” in one tab can impact — and sometimes crash — the operation of the entire browser. Web 2.0 has brought about an array of browser-based applications and activities that require a more robust, stable, multiprocessing browser with each process assigned to its own memory space and associated data structures — which is basically how DESQview operated. Indeed, when I pointed this out during yesterday’s SquawkBox, someone labeled Google Chrome as “DESQview for the cloud.” Talk about “Back to the Future“!&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #chrome #desqview #google #qemm #web20 #webdev #webos&lt;/p&gt;</description>
      <pubDate>Fri, 05 Sep 2008 22:41:54 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11345</guid>
      <category>chrome</category>
      <category>desqview</category>
      <category>google</category>
      <category>qemm</category>
      <category>web20</category>
      <category>webdev</category>
      <category>webos</category>
    </item>
  </channel>
</rss>
