technojamin

Here's a great video by Ordinary Things that talks about the development and proliferation of satellites over the past century, space debris, and how things could play out in the near future: https://www.youtube.com/watch?v=90N6IZnV85c

Especially relevant because Starlink has been causing numerous near-collisions over the past few years.

That's exactly why the author included it. Your definition seems appropriate at first and is probably what most people assume: "ours" refers to "my current branch" (HEAD), and "theirs" refers to "the other branch".

This breaks down during rebase, where the terminology gets reversed. The definitions are more accurately:

- "Ours" refers to "the branch whose HEAD will be the 1st parent of the merge commit" (during merge) or "the branch who will get commits applied on top of its HEAD" (during rebase)

- "Theirs" refers to "the branch whose HEAD will be the 2nd parent of the merge commit" (during merge) or "the branch whose commits will be applied on top of the other branch" (during rebase)

This gets a little more complicated during "octopus merges", where there are multiple "theirs" branches.

Elixir/Rust is the new Python/C++, and Rustler makes the communicating between the 2 languages super easy: https://github.com/rusterlium/rustler

VS Code isn't actually that bad with its extension and application updates. When an extension has been updated, it'll try to load the new version in-memory (if the extension supports it), otherwise it'll add a badge to the Extensions panel icon in the sidebar, leaving a subtle reminder that you need to restart in order to get the new extension update. For updates to VS Code proper, it adds a badge to the settings icon. No popups or notifications. You can also disable auto-updating for extensions and the application if you find the badges distracting.

Now, if certain extensions try to get your attention with notifications or automatically opening release notes, that can absolutely be a problem. Extensions vary wildly in quality, since the barrier for publishing one is effectively nothing. These leaves the job of curating good, non-spammy extensions up to the developer.

WSL2 uses a Hyper-V virtual machine [1], which is a native hypervisor [2] and doesn't come with most of the performance costs of software VMs.

[1] https://en.wikipedia.org/wiki/Hyper-V

[2] https://en.wikipedia.org/wiki/Hypervisor#Classification