If people aren't getting their work done, then they should be having discussions with their manager that eventually lead to pip or firing if not resolved. If they are getting their work done... Who cares if I do a "non work thing" at a "work time"?

And also, a decent chunk of alcohol consumption must be solo? I'd bet alcohol is broadly more social, but I would also wonder if that would change if more public gathering places served weed in some form.

There is a ton of tools and custom logic used by/with/for the GN ecosystem in chromium that I imagine would be difficult to port.

This tool is substantially less complex than Bazel, nor is it a reimplementation of Bazel. Ninja's whole goal in life is to be a very fast local executor of the command DAG described by a ninja file, and siso's only goal is to be a remote executor of that DAG.

This is overall less complex than their first stabs at remote execution, which involved standing up a proxy server locally and wrapping all ninja commands in a "run a command locally which forwards it to the proxy server which forwards it to the remote backend" script.

A handful of other areas are configured using Starlark in chromium. This particular use is in a very different capacity than Bazel - the Bazel equivalent in chromium is GN, and I have not seen any signs that GN will be replaced any time soon.

Saying that Microsoft is "Rewriting Windows in rust" suggests you might not be as informed as you think... Very specific components with history of performance or security issues are getting ported in a very uncoordinated effort. Windows will be primarily C, C++, and C# for a very long time to come

In case you don't see my comment on the parent, it's an Azure VM thing: https://news.ycombinator.com/item?id=42788912

Look up the difference between Dv5 and Ddv5 VMS, for instance, or anything talking about azure VM temp disks for more info.

This isn't a github runner issue, it's an Azure VM issue. They use Azure VM SKUs with temp disks, and windows VMs on those SKUs by default spin up with C on a remote-backed, persistent file share and D on the local temp disk. The remote-backed file share OS disk is absolutely slow, especially if they're using Standard HDD or Standard SSD disks. You can spin up your own VMs that use Premium OS disks for slightly better performance, but if you are doing anything serious on an azure VM, you should use the temp drive (which, by the way, mounts to /mnt on Linux) or ephemeral OS disks.

(And also this is all for v5 and earlier skus and changes slightly for v6 skus but whatever).

Surely there is a middle ground for contributions which you don't really care to retain ownership of? I don't sign CLAs for projects I want to form a long term contributor relationship with, but if I am just trying to fix a small bug that the (probably corporate) owners don't care to fix themselves, I'll sign that code away without hesitation.

Someone already said The Rest is History, but one of the presenters of that podcast Tom Holland (not the actor) has also written extensively about the history of the catholic church in Millennium and Dominion. Highly recommended.

Which take millions of dollars and huge teams to make. These take one bored person, a sentence, and a few minutes to go from idea to posting on social media. That difference is the entire concern.

Is there a way to get phones to you or information about how to do this myself? I am sure I could find similar programs if I looked but it sounds interesting.

I don't think it's true that C# isn't taken seriously at Microsoft - some of the frameworks on top of C# come and go, but I worked on JS on WinRT briefly and can say it was never, ever "taken seriously" in the way the core C# language and runtime is. If you want to work with azure or windows, C# will be the obvious best choice for the foreseeable future, and if you want to work with C# outside of those verticals I don't think it's a bad or dead end choice either.

Lots of positive comments here that are mostly correct, but I will say that if you're working with more junior or just less technically passionate people, Starlark is a lot for them to wrap their heads around. "Python, but not", no Starlark.exe (always hosted in different exes that provide different functionality), poor editor highlighting/intellisense, and the concept of writing configuration in the same language which interprets that configuration are all hurdles that I've found some have difficulty with. DSLs encoded in yaml and JSON have a lot of the same problems, but I still get a lot of feedback that Starlark feels more complicated.

Strong disagree. So much space dedicated to touristy pictures that could be used for books instead. Very poorly laid out and hard to get around all of the people taking selfies, and even once you do I found their book selection to be lackluster (at least for historical non-fiction)

Isn't the problem here the flaky and long running PR gates? There's room for nuance to say "small PRs are a north star but large PRs are sometimes OK too"