Scott Hanselman recently blogged about job processes in Google Chrome and the upcoming Internet Explorer 8, and demonstrated the benefits of putting each browser tab in its own process. He also ate away at the notion that creating and communicating between processes is slow, calling attention to Moore’s Law and how it affects computer speed and memory amount, which keeps making slow things like process creation faster.

So when will Mozilla follow suit with Firefox? A discussion at mozillaZine makes it sound like it might be a long time, if ever. But with fears that Chrome might eat Mozilla’s candy starting to run about, it might make sense to engineer the next major version of Firefox to use separate processes for each tab.