It's could be unfixable without a significant performance penalty, but at minimum they could make safari do proper process isolation like every other browser does.
Right, but that was before they knew about this exploit. My point was that even if they decided they needed to urgently switch to a multiprocesses architecture because it's the only way to mitigate this exploit, they might not be done yet.
