<story><title>Show HN: Breach – A modular browser built on Chromium and Node.js</title><url>http://breach.cc</url></story><parent_chain><item><author>shawnz</author><text>What about this doesn&amp;#x27;t also apply to Firefox? It too is open source and modular, and also written in Javascript (though combined with XUL rather than HTML, and using Gecko instead of Webkit).</text></item></parent_chain><comment><author>swift</author><text>That was my reaction as well. I was pretty interested to see a browser genuinely written entirely in JavaScript, which would at least be a new thing.&lt;p&gt;Since it seems like the developers are posting in this thread, could you talk a little about the differences between Breach&amp;#x27;s approach and Firefox&amp;#x27;s? I suspect they must exist mostly in the node.js layer - which tasks is that layer responsible for?&lt;p&gt;(Edit: I see you replied to the parent comment while I was writing this one. =)</text></comment>
<story><title>Show HN: Breach – A modular browser built on Chromium and Node.js</title><url>http://breach.cc</url></story><parent_chain><item><author>shawnz</author><text>What about this doesn&amp;#x27;t also apply to Firefox? It too is open source and modular, and also written in Javascript (though combined with XUL rather than HTML, and using Gecko instead of Webkit).</text></item></parent_chain><comment><author>spolu</author><text>It does apply indeed! We went one step forward and didn&amp;#x27;t provide any functionality to the browser to make it entirely built out of modules. And we did it on top of Chromium Content Module.&lt;p&gt;The basic motivations are totally the same. I also believe that is&amp;#x27;s probably way simpler to rewrite an entire web browsing experience on top of Breach.</text></comment>