2e8a9d6bb6935a54

Want to make a branch ?

git checkout

Want to make switch branches ?

git checkout

Want to get a specific file version ?

git checkout

Want to get remove changes to one file ?

Believe it or not, also git checkout

Apparently VMWare knows what's up

Via @mountain_ghosts via The Register

Via Toggl

Playing a game

Visual Studio Code

From the Apollo 11 github repo: https://github.com/chrislgarry/Apollo-11/blob/b56b8c3d03e810a6ceb69e1c0874d4c89d2c32f6/Luminary099/LUNAR_LANDING_GUIDANCE_EQUATIONS.agc#L666C1-L667C1

Via DesignerNews: Getting help from an engineer

Original tweet: https://twitter.com/DesignUXUI/status/576432203560685568

A collection listing Achievements that were rejected when creating the GitHub Profile Achievements feature.

This repository attempts to list them all.

    // We play this game because we want this to be callable even from places that
    // don't have access to CallFrame* or the VM, and we only allocate so little
    // memory here that it's not necessary to trigger a GC - just accounting what
    // we have done is good enough. The sort of bizarre exception to the "allocating
    // little memory" is when we transfer a backing buffer into the C heap; this
    // will temporarily get counted towards heap footprint (incorrectly, in the case
    // of adopting an oversize typed array) but we don't GC here anyway. That's
    // almost certainly fine. The worst case is if you created a ton of fast typed
    // arrays, and did nothing but caused all of them to slow down and waste memory.
    // In that case, your memory footprint will double before the GC realizes what's
    // up. But if you do *anything* to trigger a GC watermark check, it will know
    // that you *had* done those allocations and it will GC appropriately.

Relevant code on line #269

If only string maps were known to human kind :)