https://www.shadertoy.com/view/tXSBWt

Here is a version with a smoothly moving red circle; notice how you can now move your eyes smoothly around the screen as you track the circle.

If the customer requests too many refunds (say 3-4 within a few months) their Apple ID is likely to be banned from making further purchases.

The basic technique for rendering gaussian splats is kryptonite for this architecture, essentially implementing every worse practice for rendering on a mobile GPU:

* Tons of overdraw (overlapping splats)

* Tons of alpha blending

* Millions of splats in the distance generate a lot of tiny triangles resolving to a single pixel

* Long thin splats in the foreground generate triangles that cover multiple tiles

These are all the ingredients you need to bring a mobile GPU to its knees! Any desktop GPU (including most laptops) will be far less sensitive to these issues, even if it's not very powerful. It's a fundamental issue of architecture rather than one of raw FLOPs.

[1] https://en.wikipedia.org/wiki/Tiled_rendering

Can I drive through here? [Yes] [No]

When this is happening, the car is stopped and lets the passenger know that it’s reaching out for remote help to figure out what to do. For me this has happened two times across my 125 Waymo rides (571 miles) so far, and was resolved in under 20 seconds. Though I must say, 20 seconds feels like ages when you’re in the car and blocking traffic!

It just seems like a more obvious “center” for an ancient person; the mechanics are so easily detectable from the outside, while the liver sits silently.

Any idea if this means you can actually choose a different browser, or are you choosing a different WebKit wrapper (e.g. the current version of Chrome on iOS)?

The article attributes the stat to "a study by Business Insider" but the reference links to an article in The Atlantic which: A) doesn't support the claim and B) is mostly dedicated to debunking it.

He is basically saying they have no leverage to stop him speaking out once he’s been fired (which they might if he remained an equity holder).

Advantages:

1) Your scanning labor is spread out across your entire visit

2) No need to unload and bag everything at the end

3) You can see a running price total

Is that last point the reason why supermarkets moved away from them? Because they don’t want you to budget in realtime?

Here's a video from someone (who I don't know) from late March: https://twitter.com/sidtriv/status/1641641533240905728

Unclear if Google would still be allowed to default to Google search on their reskinned version of Apple’s browser (branded as “Chrome”, even though it isn’t). But that’s mostly up to Apple, since they write the rules for the App Store, the only way to install software on Apple’s OS. Google might have to maintain their $45bn/year tribute for that privilege.

This year, they've _finally_ introduced a higher-level API that does what you're describing, but it's still in beta: https://developer.apple.com/documentation/cloudkit/cksynceng...

I think this could be fair for background actors _if_ it was scoped to a single project.

Come in, get scanned, maybe do some mannerism mocap and then get the negotiated day rate. The rate for a single day should be higher than it is currently, but still less than the studio currently pays for multiple days of background work.

This would be closer to a win-win: the background actor gets paid more money for fewer hours of work, and the studio spends less money overall on background actors.

One way is to use object pooling, but doing so in JS can be brittle because you have to remember to manually call `Pool.release(obj)`, `obj.free()` or whatever method you’ve chosen to return an object to the pool.

If a developer forgets to do this, you could exhaust the object pool, or if it’s growable, cause a memory leak! In a game’s update loop that could happen very quickly.

With this new feature, you could grab a short-lived object from the pool and automatically return it to the pool at the end of the method or loop.

Example - imagine this is inside an update method called 60 times per second:

  for (const enemy of enemies) {
    using pos = Pool.getVec3();

    // do stuff with pos

    enemy.setPosition(pos);
  } // pos is returned to pool automatically  

* Big performance hit when you use it in a hot loop like this - the disposal could be happening ~10,000 times per second.

* Harder to remember to fill all your loops with try…finally, ugly to have double braces anytime you’re using a pooled object.

* It’s an abuse of syntax if you’re not actually catching any error.