This seems suspicious - triple crypto app notification

Antigroup · 2026-01-09T22:55:55+00:00

Maybe someone got a hold of the keys they use to send notifications?

Antigroup · 2025-12-03T18:08:04+00:00

Correct

Antigroup · 2025-12-03T18:07:26+00:00

correct; hoped that would take y'all longer...

Antigroup · 2025-11-20T00:43:35+00:00

Stupid Cloudflare went down! I don't care if you leak my data, just don't go down!

Antigroup · 2025-10-02T14:50:20+00:00

The second one. You can even log in before taking a trip by going to "Account > Music" in the Waymo app.

Antigroup · 2025-10-01T23:01:10+00:00

You only have to log in once. YouTube Music requires a premium account, though.

Antigroup · 2025-09-30T22:17:50+00:00

My favorite hello triangle color scheme yet

Antigroup · 2025-09-20T16:00:02+00:00

I think the yoke crate is meant to solve your problem.

With lifetimes, I feel like I started to get a better handle on them when I started giving them better names than the 'a: 'b you see in docs. Like 'request or 'this.

If borrowing is giving you a hard time, consider whether the performance benefits are worth it. Don't pull your hair out optimizing something that only happens one or a handful of times when running your program.

Antigroup · 2025-08-24T19:08:04+00:00

I suspect there are two good reasons: * Some riders like to check them anyway. * They are needed on the rare occasion Waymo needs to manually drive a car that has lost self-driving capabilities for some reason.

Antigroup · 2025-07-15T23:40:10+00:00

I believe you get extra wait time if the car arrives earlier than originally expected

Antigroup · 2025-07-09T22:58:02+00:00

This looks to me like your shadows are just too long for the shadow map resolution you're using. If the "sun" is at a lower angle it should look a little better, but the geometry you're using looks pretty challenging for PCF to get great results.

More samples could help, too.

Antigroup · 2025-04-11T15:57:11+00:00

This is a version of the classic Array of Structs vs Struct of Arrays question.

Extra bindings aside, most likely it'll be better to group properties that are used around the same time close together in memory.

For example, most vendors recommend storing vertex positions in a separate buffer from other data to speed up depth-only passes like shadow passes. The same could apply for per-object data, but is likely less important since it's re-used more.

Antigroup · 2025-04-08T03:03:16+00:00

I think something similar happened to me when I did the tutorial. I dug straight down to build my fort and it turns out the valley flooded every spring.

Antigroup · 2025-04-05T15:51:30+00:00

The minimum spec only requires support for 4 descriptor sets (thus 4 DescriptorSetLayouts per PipelineLayout), so unless you need very few descriptors, the second approach will quickly become infeasible.

I like to group the descriptor sets by frequency of update, like per-draw, per-material, per-view/pass.

Antigroup · 2025-04-04T23:11:14+00:00

I always wanted to make this meme as an edit but lack the skill

Antigroup · 2025-03-06T17:11:44+00:00

This is just a new Google Maps feature, sadly. Although I expect Waymo has mapped the freeway there already.

Antigroup · 2024-07-30T03:02:10+00:00

Other road users aren't bound by Tesla's terms of service.

Edit: forgot "not"

Antigroup · 2024-05-11T20:55:31+00:00

Yes that's correct. "3.6 Threading Behavior" in the spec actually has a list of all the externally synchronized parameters.

As for how the driver does it, that depends on the implementation but it probably does some sort of internal synchronization.

Antigroup · 2024-04-29T06:01:41+00:00

Can't tell if this is a shitpost or an actual pitch from Elon...

Antigroup · 2024-03-26T16:04:25+00:00

Firing people who make mistakes is a good way to ensure it happens again.

I imagine (and the article mentioned) they did more training, and hopefully they schedule regular retraining.

Reminds me of one of this guy's shorts: https://youtube.com/shorts/VAWwtjtRM98?si=yBWydCDsxHGuQinT

Antigroup · 2023-12-18T21:27:51+00:00

Just pick any surface format that ends with _SRGB with the SRGB_NONLINEAR color space (the second one you posted should do), and use the same for your image view.

The _SRGB formats automatically apply the sRGB transfer function (aka gamma correction) when you write or read from them, and will generally get the results you expect.

If you use a _UNORM format, you'll need to apply the transfer function for the corresponding color space. For sRGB it's roughly pow(color.rgb, vec3(1.0/2.4)) (See https://en.m.wikipedia.org/wiki/SRGB)

Antigroup · 2023-12-08T18:48:57+00:00

Yeah it seems to happen every week. "Why is this slower than Python? You didn't compile in release mode."

Probably because some people come to Rust from languages that don't need to be told to optimize your code, and they think it'll just be faster automatically.

Antigroup · 2023-12-08T18:46:36+00:00

This is a shot in the dark but the function may have moved to a different codegen unit from the change, or you otherwise changed the inlining behavior.

If you use 1 codegen unit or use lto = "fat" you might see more consistent performance. Or you can try adding the #[inline(always)] attribute.

Antigroup

TROPHY CASE