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"?
In an agile world with an infinite backlog there's no such thing as being done with work. If you could be working on more work things during work time, they probably want that. Maybe you don't like that but c'mon now. It's clearly what they're after.
Then maybe it doesn't need to be done on a strict work/non-work schedule everyday? If one is an hourly employee, then sure, they should be doing work things when on the clock... but if they are salaried, part of that is not having to clock in and out to switch between work and non-work tasks, and not being a strict work/non-work schedule.
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.
GN at least used to generate Ninja files. So I suppose now it will be generating Siso files?
edit: asked and answered, Siso is a "drop-in" replacement for Ninja, so presumably it can read .ninja files, and so GN probably didn't need to change much to accommodate it.
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
Also those are two different skill sets. Writing critical sections of an OS is not the same thing as writing a compiler. And completely agree, windows to what I have read, is being deliberate and isn't doing a total rewrite at all. Thanks for chiming in so I could type less.
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.
FWIW CLAs do not sign away your ownership in code. It merely gives the project the right to use your code via a license
You know how you sign those end-user *license* agreements, which do not give you ownership in the code of those applications?
That's the same principle at work here. You are licensing certain rights in your work to another entity. Generally, the license is giving the right to, inter alia, reproduce and distribute your code in perpetuity.
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.
Not read Millennium, but Dominion is brilliant. its not just the history of the church, it explains how the West came to be what it is and the influence of Christianity.
It is also a useful corrective to the Western tendency to see its values and attitudes as universal, even where they are a product of a particular history and culture.
Second the recommendation on Millennium, just note that for some stupid reason the US publisher decided to retitle the book "The Forge of Christendom". So if you're in the US you won't find it under its real title.
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.
