Platform Development • Re: e10s support question

In general, it would be logical to run the main UI in a separate thread. A web page shouldn't be able to block the entire browser. Mozilla got it wrong from the start, in my opinion. But the main problem is that the Java VM implementation is essentially single-threaded. Of course, you can run multiple threads, but these threads can't share objects. This isn't multithreading at its core. True multithreading begins when objects can be shared and there's automatic thread suspension when multiple threads access shared objects simultaneously. But it's not implemented that way...