Activity for February 24

Posted a comment

Jay's Profile

Member since September 8, 2008

  • Name

    Jay

  • Location:

Favorite Files

Recent Posts

  1. Comment - Windows XP to Windows 7 upgrades: Difficult, but not impossible

    (Feb 24, 2009 - 2:25 AM)

    One of these days I wanted to figure out how early a Windows version you can go for an upgrade to be possible. I mean, the only upgrades I've ever done personally was from DOS to 3.1 to 95, and then another machine from XP to Vista and yet one more machine from Vista to 7 beta. I know 95 can go to 98, and 98 can go to 2000 I think.
    I should try a personal experiment to see if I can go from 3.1 to Windows 7 from upgrades alone.

  2. Comment - Evidence tabs will get more attention in future Firefox releases

    (Sep 13, 2008 - 4:15 AM)

    Last I checked, Chrome uses around 25 MB of RAM for the main host process and maybe around 7 MB for an empty sub process. (These numbers are loose, ofc. That's just what it was on my system). I wouldn't say it's a 5% increase... it's clearly more like 25-30%, but ok. It's still not much memory on a whole, the browser is just so light. (Which is why I love it so much).

  3. Comment - Evidence tabs will get more attention in future Firefox releases

    (Sep 8, 2008 - 9:52 PM)

    What Chrome does is something completely different... Each tab isn't really a "tab" per se. They are a bunch of instances of individual browsers snapped together in a single "window."
    When you do this, it's easy to move it about or detach it. All you're doing is detaching the GUI of that web page from the rest, or moving it around. The browser itself remains entirely intact.
    What Firefox does is handle things on a thread-by-thread basis, instead of separate instances or the browser (separate processes). This makes the browser on a whole use less memory with many tabs, but the side effect is clunkier interaction when trying to manipulate these tabs, since it's not very efficient to rip a thread out of one process and recreate it inside another...
    In fact, I think Firefox should drop trying to use this method altogether and just go multi-process like Chrome. It's just *SO* much cleaner and efficient, even if it takes more RAM.