|
! 4 @ 0 @ 4 !
Что-то пошло не так. Главная страница
Факт о медицине:
But back to memory consumption - Google Chrome consumes 185 MB of memory in this configuration versus about 60 MB for Firefox (in terms of: 8.5 MB / page for both), but three times more virtual memory (about 350 MB versus 115). It turns out that not everything is so bad and the overhead with this architecture is not particularly large, although on computers with little memory it is unlikely to be so fast, especially if there are many applications in parallel - frequent use of the paging file can significantly slow down the work.
Медицинские новости:
Google is clearly making its operating system out of the browser - both architecturally and conceptually. Having previously tested Gears on a large army of users, partially transferred their services to it and captured the minds of many web developers (even MySpace), they integrated it into the browser and now no modules are needed - everything works out of the box, which users so dreamed of ( without even suspecting) and the developers. The main competitor, I would single out not Firefox at all, as everyone compares, but Adobe AIR - in fact, each tab in Google Chrome is an instance of the same AIR. Both have the same engine, both have modern and fast JS engines, integrated Flash and other required plugins. Both projects act as an ideal platform for AJAX web applications, the only thing is that Google has a shorter path to the user, after all, Chrome is not only a platform, but also an end product (albeit, in fact, attached to the load of the platform).
|
