It all started with a small, relatively unknown browser named MyIE in 1999, that was then renamed to Maxthon (version 1) on 2003, from there, a journey of exciting features additions, dramatic features omissions and lots and lots of forum posts followed, until 14 years later, when the latest version of Maxthon – version 4- was released. Just 4 major releases? I wonder what would happen If chrome developers created Maxthon. Hmmm..
Nevermind, this isn’t interesting. You are not reading this for a history lesson full of material copied from wikipedia, are you? What’s really interesting is how the developers of Maxthon managed to survive all the widely-changing world of technology without being left in the dark corner of irrelevance. A feat achieved only by a few number of applications.
More information about the upcoming major release has been revealed in the last two IRC channel meetings with Maxthon’s main developers, and as expected, Johnnylegend (you should have read this name several times by now) posted both logs on his blog.
If you have been following this blog you would know that a new engine will be available to Maxthon 3 in addition to Trident (IE’s rendering engine). the new engine is “faster and more [compatible with] standard[s]” and opensource, this means we were left with two choices: Webkit and Gecko, this time we know that it’s officially Webkit and this is definitely good news. 😀
Maxthon’s forum admin abc@home, has recently posted an insighful summary of the differences between Google Chrome’s multi-processes feature and Maxthon’s isolator:
Essentially, the anti-freeze technique is to make the user interface (menu, buttons, toolbars etc) independent of the tabs, which contain the browser controls and where problems often arise, and make each tab independent of each other. Chrome uses multi-process to achieve this while Maxthon 2.x uses multi-thread to acheive the same. Yet whether multi-process or multi-thread, it is not possible to be totally independent. There must be inter process/thread communications to be a unity.
Generally processes are more independent than threads. But a thread consumes less resources than a process, and a thread works more efficiently with other threads of the same process than a process working with another processes. Before 2.5.1, the multi-thread technique was limited by the traditional windows framework and did not work as effectively as intended. Maxthon 2.5.1 uses a new windows framework to perfect the implementation.
To read more about the Isolator feature of Maxthon 2.5 visit Maxthon’s official blog.