<?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>Eficiencia on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/eficiencia/</link><description>Recent content in Eficiencia on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Wed, 30 Nov 2016 08:34:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/eficiencia/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing efficient JavaScript</title><link>http://karpoke.ignaciocano.com/2016/11/30/writing-efficient-javascript/</link><pubDate>Wed, 30 Nov 2016 08:34:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/11/30/writing-efficient-javascript/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This entry describes simple techniques to fulfill the JavaScript compiler
optimization process which results in faster running code. Especially in
games you immediately notice frame drops and when the garbage collector has
to hit in with a big stack of work to do.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Felix Maier | &lt;a href="https://medium.com/@xilefmai/efficient-javascript-14a11651d563#.k634iq2t7" title="Writing efficient JavaScript"&gt;medium.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>