posted July 14, 2014 #
I must admit, despite not fully understanding the technology behind this
Breach browser I am fully intrigued. The claims that it is written "entirely in Javascript" (on top of Chromium and Node.js layers) sounds like a great recipe for a browser with a lot more possibilities, as its development is largely on the shoulders of curious hackers. This summary introduction to the project is compelling:
The initial motivation to create Breach was to create a browser whose state (tabs, cookies, extensions, etc...) would be completely untangled from the machine it runs on, so that users could project that state on any machine running Breach easily. The idea was to let users get control of any machine around them transparently by making it very easy for them to push their state onto these machines. Think of it as tab syncing as seen in Chrome, Firefox, Safari, on steroids and built to be used on machines you don't necessarily own (which is a strong limitation in existing systems).
Count me in! Going to give this a spin.
