pooling

The problem is that in order to do true risk pooling, you need to be able to charge based on risk.

Object pooling is essential for performance in Unity 3D if you're dealing with large amounts of game objects.

If you need more objects than would fit on the stack, pooling might be a better choice.

Sure it's yours, but they are pooling money from all users and investing it in the meantime.

The same BMW in Europe is marketing car clubs and car pooling to save the planet, while in China and India the message is total opposite about aspiration and horsepower.

> The problem is that in order to do true risk pooling, you need to be able to charge based on risk.

This kind of pooling is pretty basic CS knowledge, and thus is a very popular technique in many applications, libraries, etc.

No, object pooling is not for that case and definitely doesn't help with that.

You're ignoring the pooling savings which come from being able to easily coordinate shared rides due to a huge installed rider base.

Object pooling is a useful tool when architecting something huge and performance sensitive.

We used object pooling in C++ 2 decades ago in real time applications.

So it's surprising and interesting to read that the author of this article clearly thinks that there are still benefits to object pooling.

Pooling and in-place reuse are two different things, to be sure.