>>17
cool, that's encouraging. I'd probably only support one active tab at a time. Or maybe tabs could be supported, but the unviewed pages would be written explicitly to disk in a format that is quick to read and preserves the state of the running javascript. Alternatively, if running on a machine with virtual memory and an OS that can page stuff out to disk, then care could be taken such that a single web page and all state of its executing javascript would be contained within a single virtual memory page, or the fewest amount of pages possible. Then the browser could suspend the javascript execution of the web page and never refer to memory on those (memory) pages, allowing the OS to page the web page data to swap if needed. Running javascript and javascript timers would need to be suspended, which might break a few websites. But if they aren't designed to recover under such circumstances, then those websites are complete shit, although that doesn't change the fact that you may be forced to use them, so I don't know...