All updates are manual, and are done via pull requests. Check everything in-queue: https://github.com/microsoft/winget-pkgs/pulls

Existing versions don't tend to have their metadata updated (I'm not sure winget would accept it). Only new versions are supported.

You can see all the checks that go into cpu-z updates with the latest PR: https://github.com/microsoft/winget-pkgs/pull/349095

which you can install with:

   winget install --exact --id CPUID.CPU-Z

I wish Java had a proper compiler.

1) No immutable types. My work team is a huge user of immutable data stuctures in Java to make sure data passed around to other teams isn't changed. Go doesn't really have a good way to do this.

2) Refactoring can be really annoying (or at least really noisy) because of public/private being defined by capitalization of method/field names.

3) Error handling isn't great. I love Go's errors being just normal values, but the `error` interface is awkward when trying to figure out what kind of errors can be thrown without having in-depth knowledge of the kinds of errors that can be returned. We regularly need to make different decisions depending on the kind of error returned. Knowing which errors can be returned in Go is not defined by the method being called (only in comments).

That's the policy being followed here. If you remember back a few weeks, Iran killed likely 30,000 of its own citizens. On top of that, they will not negotiate about medium and short-range missiles or stopping of nuclear production.

A power like that that happily goes after it's neighbors, directly or indirectly is a threat to everyone.

Specifically in Gmail Settings:

> Smart features: Turn on smart features in Gmail, Chat, and Meet - When you turn this setting on, you agree to let Gmail, Chat, and Meet use your content and activity in these products to provide smart features and personalize your experience.

My wife turned this off because she didn't want typing suggestions or even grammar correction. After disabling the feature, she was much happier.

(googler, opinions are my own)

https://reason.com/2017/05/31/florida-man-jailed-180-days-fo...

https://www.hyrumslaw.com/

> With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.

For chargebacks, the merchant has to pay at least a $15 fee on every chargeback, regardless of the outcome of the result. It's why many merchants prefer for you to contact them and ask for a refund rather than going through the chargeback process. For small purchases, merchants tend to just refund rather than dealing with an angry customer that's going to charge back.

But just closing the bank account will stop auto billing (it's considered a decline). So if you closed the account, it would just stop paying for whatever it is, and then cloud may lock the gcp account until it's paid. (I'm not 100% sure what cloud does with unpaid invoices).

Gear -> All Settings -> General tab (default) -> Smart features: Turn on smart features in Gmail, Chat, and Meet

Linked help page: https://support.google.com/mail/answer/15604322

https://github.com/search?q=repo%3AFFmpeg%2FFFmpeg+%40google...

And they have done large pushes in the past: https://security.googleblog.com/2014/01/ffmpeg-and-thousand-...

I regularly have multiple commits being worked on at a time across different parts of the codebase. If I have to sync to head (or any rebase) and one of my side branches that I'm not actively working on hits a merge conflict, I don't have to deal with it in that moment and get distracted from my work at hand (ie: I don't need to context switch). This is a big productivity win for me.

If you want some other points, check out: https://fallthrough.transistor.fm/43#t=0h31m5s

Some points from the episode:

* With no separate index vs commit, (everything is just a commit), you don't need different commands and flags to deal with the different concepts, they are all just marked together. In JJ, if you want to stack/stage something, it's just a normal commit (no reason to have different concepts here).

* You don't have to name/commit a change at all. Every time you run any JJ command (like `jj log`, or `jj status`), it will snapshot the changes you have. This means that if you want to go work on some other branch, you don't have to go and commit your changes (they auto-commit, and you don't have to write a description immediately), then update to master branch and start working again.

* Or you can just `jj split` (https://jj-vcs.github.io/jj/latest/cli-reference/#jj-split), and split a working changeset into 2 separate commits.

This is a Google-internal only GA. JJ is available externally just fine. Google is mainly a linux-dev shop, with all other platforms being second-class citizens.