Google’s Chrome browser launches & loves tabs & users

Google Chrome

Google on Google Chrome – comic book

My time with Chrome on the Windows partition of my old MacBook mirrored in Twitter, echoed by FriendFeed:

Published by attilacsordas

bioinformatician, digital health entrepreneur, ex mitochondrial-stem cell biologist driven by healthy lifespan extension, free variable

8 thoughts on “Google’s Chrome browser launches & loves tabs & users

  1. I downloaded Chrome this morning (although it said it was released yesterday, I couldn’t get the link to work.

    Played around with it for a while, but switched back to Firefox. I couldn’t figure out how to load my bookmarks, or maybe since I have them all in deli.cious they’re not compatible?

    It did appear to load some sites more quickly, but some really seemed to drag along, maybe because my cache is not full or something.

  2. i prefer to have firefox or explorer with the google bar, easier to search different google functions (such as images or scholar).

  3. i keep learning about more and more little advantages and quirks with Chrome, such as with security, for example; now if only they would take care of it’s cookie management glitches…

  4. Soft-updates guarantees that the only filesystem inconsistencies on unclean shutdown are leaked blocks and inodes. To resolve this you can run a background fsck or you can ignore it until you start to run out of space. We also could’ve written a mark and sweep garbage collector but never did. Ultimately, the bgfsck is too expensive and people did not like the uncertainty of not having run fsck. To resolve these issues, I have added a small journal to softupdates. However, I only have to journal block allocation and free, and inode link count changes since softdep guarantees the rest. My journal records are each only 32bytes which is incredibly compact compared to any other journaling solution. We still get the great concurrency and ability to ignore writes which have been canceled by new operations. But now we have recovery time that is around 2 seconds per megabyte of journal in-use. That’s 32,768 blocks allocated, files created, links added, etc. per megabyte of journal.

Comments are closed.