<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Misael Zapata</title><link>http://misael.org.s3-website-us-east-1.amazonaws.com/</link><description>Personal site of Misael Zapata</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 05 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://misael.org.s3-website-us-east-1.amazonaws.com/index.xml" rel="self" type="application/rss+xml"/><item><title>node-vmm: VM isolation that feels like spawning a process</title><link>http://misael.org.s3-website-us-east-1.amazonaws.com/node-vmm-instant-vms/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><author><name>Misael Zapata</name></author><guid>http://misael.org.s3-website-us-east-1.amazonaws.com/node-vmm-instant-vms/</guid><description>&lt;div class="featured-image">
&lt;img src="/node-vmm-instant-vms/images/cover.png" referrerpolicy="no-referrer">
&lt;/div>1 The comfortable lie about containersThere is a polite fiction in modern development that everyone accepts because it is convenient: we pretend Docker containers are fast and lightweight. And they are, if your reference point is provisioning bare metal in 2005. But as my tools needed to isolate workloads more frequently — and more dynamically — I started feeling the drag of depending on a giant external engine sitting between me and what I actually wanted.</description></item></channel></rss>