35 ms·
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. Since it
by swift 12y ago
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.
Since it seems like the developers are posting in this thread, could you talk a little about the differences between Breach's approach and Firefox's? I suspect they must exist mostly in the node.js layer - which tasks is that layer responsible for?
(Edit: I see you replied to the parent comment while I was writing this one. =)
- spolu 12y agoI've detailed a how we ended up building Breach as it is in the introduction of that page: http://breach.cc/hack http://breach.cc/hack Basically, the idea is to take the Chromium Content API and expose it to JS (that's similar to Firefox). Doing it we figured, why not add some APIs to do interesting stuff in JS as well... and that's how we embedded NodeJS and exposed the Content API within a NodeJS tread.... So you have access to all the nodeJS modules while building your own modules for Breach... makes it fairly convenient :)
- Excavator 12y agoHow do you define "genuinely written entirely in JavaScript"? Is it covered by something like links/lynx in a JS based RISC emulator¹ or the Firefox OS web browser app²? [1] http://s-macke.github.io/jor1k/ http://s-macke.github.io/jor1k/ [2] https://github.com/mozilla-b2g/gaia/tree/master/apps/browser https://github.com/mozilla-b2g/gaia/tree/master/apps/browser
- swift 12y agoThose are interesting projects for sure, but for me neither of those really qualify. I'd want to see the core browser algorithms written in human-readable JavaScript - things like HTML parsing, CSS layout, and rendering.