> 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
2e8a9d6bb6935a54 Now • 100%
One man's pain is another one's comedy :)
Via [@mountain_ghosts](https://twitter.com/mountain_ghosts/status/1245754158910705668) via [The Register](https://www.theregister.com/2020/04/02/boeing_787_power_cycle_51_days_stale_data/)
2e8a9d6bb6935a54 Now • 100%
Then again, the panel seems to be originally from 2016, so I'm sure perceptions changed over time
Via [Toggl](https://toggl.com/blog/save-princess-8-programming-languages)
>Playing a game >Visual Studio Code
github.com
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](https://www.designernews.co/stories/91849-getting-help-from-an-engineer)
Original tweet: https://twitter.com/DesignUXUI/status/576432203560685568
github.com
>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](https://github.com/WebKit/WebKit/blob/ab10a90523e06df54bbb8a98e1aed913f79d0af9/Source/JavaScriptCore/runtime/JSArrayBufferView.cpp#L269)
If only string maps were known to human kind :)
Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit. Link to original XKCD: https://xkcd.com/927/
This might skirt the lines between humor and horror :)
Caption: >In case of fire >1. git commit >2. git push >3. leave building
Caption: > Ask a programmer to review 10 lines of code, he'll find 10 issues. Ask him to do 500 lines and he'll say it looks good.
2e8a9d6bb6935a54 Now • 100%
There's also https://lemmy.world/c/programminghumor
This community was started a little under a week ago, and in that time, over 100 people decided that this has some sort of worth to them and subscribed. To them I say thank you for being here and for your vote of confidence. Hope you'll be here for a long time. For the new comers, welcome, I hope you enjoy it here!
2e8a9d6bb6935a54 Now • 100%
Last I counted there's actually 3 of them, besides this one :)
[Programming Humor](https://lemmy.world/c/programminghumor) !programminghumor@lemmy.world https://lemmy.world/c/programminghumor
"VPN of Sadness" really does it for me :)
2e8a9d6bb6935a54 Now • 100%
You need to verify your email address