<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jpcody)</title>
    <link>https://pinboard.in/u:jpcody/public/</link>
    <description>recent bookmarks from jpcody</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack"/>
	<rdf:li rdf:resource="http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/"/>
	<rdf:li rdf:resource="http://www.nczonline.net/blog/2010/01/12/history-of-the-user-agent-string/"/>
	<rdf:li rdf:resource="http://www.sencha.com/blog/understanding-hardware-acceleration-on-mobile-browsers/"/>
	<rdf:li rdf:resource="http://paulirish.com/2009/browser-specific-css-hacks/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack">
    <title>High Performance Networking in Google Chrome - igvita.com</title>
    <dc:date>2013-03-10T14:08:55+00:00</dc:date>
    <link>http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Chrome's network stack is, quite literally, getting smarter every day, trying to hide or decrease the latency cost of each resource: it learns likely DNS lookups, it remembers the topology of the web, it preconnects to likely destination targets, and more. ]]></description>
<dc:subject>chrome browsers performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:c030735ac2e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/">
    <title>HTML5 Rocks - How Browsers Work: Behind the scenes of modern web browsers</title>
    <dc:date>2012-02-20T00:18:24+00:00</dc:date>
    <link>http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[As a web developer, learning the internals of browser operations helps you make better decisions and know the justifications behind development best practices. While this is a rather lengthy document, we recommend you spend some time digging in; we guarantee you'll be glad you did.
]]></description>
<dc:subject>html5 browsers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:22c31e6f637c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nczonline.net/blog/2010/01/12/history-of-the-user-agent-string/">
    <title>History of the user-agent string | NCZOnline</title>
    <dc:date>2011-09-06T19:31:23+00:00</dc:date>
    <link>http://www.nczonline.net/blog/2010/01/12/history-of-the-user-agent-string/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[A couple of weeks ago, I talked about feature detection and browser detection. That post featured a little bit about user-agent sniffing and the comments continued the trend. I maintain that user-agent sniffing is an important technique to keep in your back pocket for those rare occasions when it’s needed. Before being able to do that, though, it’s useful to understand why user-agent string detection is considered to be such an inexact science. And to do that, you need to take a look at how the user-agent string has evolved over the years.

]]></description>
<dc:subject>browsers html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:b5ca8ed08320/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sencha.com/blog/understanding-hardware-acceleration-on-mobile-browsers/">
    <title>Understanding Hardware Acceleration on Mobile Browsers | Blog | Sencha</title>
    <dc:date>2011-07-18T04:47:07+00:00</dc:date>
    <link>http://www.sencha.com/blog/understanding-hardware-acceleration-on-mobile-browsers/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[There has been a lot of mentions of the use of GPU (graphics processing unit) hardware acceleration in smartphone and tablet web browsers. So far, the content has been pretty general and hasn’t provided much technical direction apart from simple advice such as “use CSS translate3d”. This blog article tries to shed some more light on browser interactions with the GPU and explain what happens behind the scenes.

]]></description>
<dc:subject>webkit browsers rendering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:739219f174db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:webkit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rendering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://paulirish.com/2009/browser-specific-css-hacks/">
    <title>Browser CSS hacks « Paul Irish</title>
    <dc:date>2011-03-13T23:19:51+00:00</dc:date>
    <link>http://paulirish.com/2009/browser-specific-css-hacks/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Nonetheless, I wanted to document every browser-specific css selector and style attribute hack I've seen. Plus there's no way to provide stylesheets to only Safari, I believe.]]></description>
<dc:subject>css browsers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:0315bc507bc5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>