Linked by Kroc Camen on Tue 22nd Dec 2009 19:50 UTC
Thread beginning with comment 400768
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2009-02-11
Carakan brings some improvements that no tech site mentions and that are relatively buried in Opera's site.
With Carakan each tab gets its own heap for memory so a common operation of javascript (garbage collection) becomes a lot faster. Basicly the speed benefits of Chrome's process separation without the stability.
More importantly with Carakan the engine cahces compiled code. That means that the second time the engine encounters the same code it's going to execute much faster. Obviously this is something that has a huge impact in real world for when you are loading multiple pages of the same site, when you are reading different news stories on a site etc.