Pimm – Partial immortalization

A Biotech Geek (micro)Blogger’s adventures through science, technology and the web…

  • email me

    [attilacsordas][at][gmail.com]
  • Attila on Twitter

  • Recent Comments

    Game on Systemic regmed
    Game on About
    Game on bioDIY
    games on Laboratory Website Awards
    xn--12c8d1a4fxc on Laboratory Website Awards
    game on Skills
    game on References
    game on Skills
    เรื่องเสียว on About
    สินเชื่อ on Skills
  • licence

    Creative Commons License
  • c

  •  

    May 2008
    M T W T F S S
    « Apr   Jun »
     1234
    567891011
    12131415161718
    19202122232425
    262728293031  

A bit of history: The official launch of Google Health, 19/05/08

Posted by attilacsordas on May 19, 2008

I am between 2 experiments in the lab, but get back to the launch of Google Health later. Here is one screenshot of my Google Health profile.

Twitter: Scott Beale

Google Blogoscoped: Google Factory Tour: Google Health Launched

Update: Late Google Health: catching up with the past, first!

7 Responses to “A bit of history: The official launch of Google Health, 19/05/08”

  1. [...] Attila Csordás at PIMM [...]

  2. [...] There’s a good early review at TechCrunch. Expect further coverage from bloggers who cover personalised medicine issues; you know who they are. [...]

  3. Mr. Gunn said

    But you speak just fine!

  4. tariely said

    электронная почта без регистрации

  5. Nice article. Thank you for this info.

  6. thanks for sharing great article !
    Teton Sports Scout 3400 Internal Frame Backpack

  7. Soft-updates is an alternative to this scheme where the filesystem keeps a list of dependencies that must be satisfied before a change to the filesystem can be visible on disk. For example, you wouldn’t want to write a directory entry pointing at an inode until the inode was initialized on disk and marked allocated. Softdep handles this by rolling back changes to metadata that don’t yet have their dependencies satisfied when we try to write a block. In this way we can commit any completed ‘transactions’ while keeping the disk state consistent. Softdep also allows these dependencies to discover operations which cancel each other out and thus nothing makes it to disk. For example, let’s say you create a temporary file and then remove it after writing some blocks, which compilers often do, if it all happens within the interval of the syncer nothing will make it to disk.

Sorry, the comment form is closed at this time.

 
Follow

Get every new post delivered to your Inbox.

Join 38 other followers