I’ve helped people with Fork before, in so much as I helped them do relatively simple things in the Git CLI that were buried in an unknown menu in Fork.

I think it’s really cool that we gave more consistent - arguably more intuitive - interfaces to interact with Git, including in IDEs, but there’s something to be said for the consistent and unambiguous nature of the command line.

So even if this can actually be easier in some specific tool, I find it’s useful to have an idea of how to do this the old way too.

This looks incredibly useful!

To be clear, that was during recovery, not a root cause.

The closest to that is this:

Neither outage was caused by a code or configuration change. Both incidents were capacity failures at their core. We failed to scale critical components before demand exceeded their capacity. Since April, monthly commits have grown from 1.4 billion to 2.9 billion. That growth explains the pressure on our systems, but it does not excuse these outages.

One could argue they still DDOSd themselves by promoting tools that produce commits at a much higher rate.

That one’s the dealbreaker. If you do all that stuff, you only have time for a grunt or two from behind your 17 inch TFT monitor.

This was a horrible day. I couldn’t even open the source code to make fun of a friend’s choice of language.

Is that salary estimate also from 2011?

There’s a more robust methodology here, which is to look at commit history, but that will only tell you how many lines were pushed and merged. That will be a greater number, by the way: say the kernel is 100 lines, somebody may have written 50, but they may have all been replaced by future patches, so The number of lines written is greater than the number of existing lines.

Regardless, I’m sure you already know lines of code is a bad metric of output, let alone effort and work.

We really all need to get along and accept each others’ opinions. Even if some people are completely wrong and think mutable by default it OK. Hehe.

Thanks, I was confused about why the helix editor might need screen sharing. Haha.

This is a dangerous metaphor. Remove the old wall and it turns out the new beautiful wall was leaning against and supported by it.

I get what you mean, it’s just that the metaphor could support both perspectives.

We know kids can take parents’ cards, right? And that people can look younger than they are? Never mind privacy concerns, the best-case scenario doesn’t look good.

I’d say I feel seen, but it’s really dark in here.

This is super interesting. I’ll admit I wasn’t even aware of this effort. Even real-time usage of Windows relies on a parallel kernel.

This sounds like it’ll create a lot of cool opportunities and reduce friction.