kyrra

Google has ~190k employees. You can't have total collaboration across that many people.

Teams will cross collaborate, but they have to be for specific projects with specific people.

I have been partially wanting one for the new one for a couple of the games, but then all four of my existing joy-cons on my Switch 1 started to have drift or other issues. So that sort of halfway saved me some money towards something I already wanted.

Though I sadly learned afterwards that you could send in controllers with drift and Nintendo would fix it for free.

I bought a switch 2 for one main reason: speed.

Switch 2 is backwards compatible with switch 1.

Switch 2 has better FPS for Switch 1 games. Like BotW stops having terrible FPS drops in certain scenarios.

Switch 2 loads games faster. There are test videos out there, but it's up to twice as fast.

I like the joycon 2 controllers ergonomics more.

California also needs a special blend that is only required in California (CARBOB). A lot of that is refined outside of the US, because there is not the capacity domestically. Cali could immediately have more fuel and cheaper prices by dropping their special requirements.

Gemini in search (AI Overview) is likely the most used LLM in the world, and ads can still surface around it.

(googler, opinions are my own. I know nothing about this outside of external info)

To steal from Twitter:

"Tim Cook took Apple from $350B to $4T"

So? That's a 11X market cap increase. In the same time, MSFT saw a 14X increase, Google saw a 20X increase, Amazon did 28X, Facebook did 35X. We're not even going to talk about NVidia.

Cook led Apple through a period where every tech company expanded. Yay for him?

(It keeps going at https://x.com/politicalmath/status/2046428057255211032 )

The criticism around that event, I believe, involved Brown University disablinf cameras trying to protect potential illegal immigrants being targeted by ice. It wasn't the lack of cameras. It was a purposeful disabling of said cameras that already existed.

I think you should spend the 5 minutes it takes to look at the winget-pkg repo to see how it works. There's lots of great documentation.

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

For windows users, this is an advantage of using `winget` for installing things. It points to the installer hosted elsewhere, but it at least does a signature check. The config for the latest installer is listed here: https://github.com/microsoft/winget-pkgs/blob/master/manifes...

which you can install with:

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

(there is a --version flag where you can specify "2.19", which the signature there is a month old, so it should be safe to install that way)

First request latency also can really suck in Java before hotpathed code gets through the C2 compiler. You can warm up hotpaths by running that code during startup, but it's really annoying having to do that. Using C++, Go, or Rust gets you around that problem without having to jump through the hoops of code path warmup.

I wish Java had a proper compiler.

Not the GP, but for really large code bases, Go is missing a few features that I've noticed:

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).

"Peace through strength"

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.

If you don't like the AI feature, Google at least lets you turn it off: https://workspace.google.com/blog/product-announcements/upda...

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)

People are jailed for contempt of court for failing to provide passwords.

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

This was well talked about in Hyrums Law, which came from a Googler as well.

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.

Prepaid credit cards tend to be a very common fraud vector (very similar to gift card scams).

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.

You're assuming the deal was anti-competitive. A lot of the time, the process is the punishment.

Chargebacks or disputes will lock your account, so definitely stay away from that path.

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).

You've never tried to free-range raise your kids then. Some friends in our neighborhood had the police called on them for riding their bikes around the block, and the cops followed the kids back to their front door and then talked with the parents.

Side projects that aren't a conflict of interest when working at Google is rather limiting. Likely less so for small companies.

The problem is that proper legislation is a balance of interests and working through the details of the policy. If you put "abortion" on the ballot, what would that mean? There are a ton of different possible policies on what is or is not permissible.

Direct YouTube link: https://youtu.be/Yg-qV6Fktjw

This. You can disable all smart features (which includes things like mail categories, AI auto-complete, and most things that look at your emails).

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

They have around at least 3000 commits, assuming this search is right?

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-...

The biggest for me: merge-conflict as first-class state within JJ.

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 talk is focused on JJ within Google.

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.

The "dig" command can get them for you

$ dig ycombinator.com mx

  ;; ANSWER SECTION:
  ycombinator.com. 300 IN MX 20 alt1.aspmx.l.google.com.
  ycombinator.com. 300 IN MX 10 aspmx.l.google.com.
  ycombinator.com. 300 IN MX 20 alt2.aspmx.l.google.com.
  ycombinator.com. 300 IN MX 30 aspmx4.googlemail.com.

The original port was slower because it was a near straight transpile impl of the original C compiler. It didn't do anything to try to speed things up, they went for correctness first. Then in subsequent releases they worked on speed improvements.

Semi related: there is an active proposal of having a go OS Target of "none" (or noos (No-OS)).

https://github.com/golang/go/issues/73608

Sounds like they want to maybe include https://github.com/usbarmory/tamago in the compiler.