Is creating new objects each frame the canonical way to go? (from Pong book example)

[Mambouna]

Hi, I was working through the pong example just now and stumbled over the part where it's recommended to create a struct to handle the paddle. This makes perfect sense, but what surprised me was that the .show() method written in the code to be copied creates new Objects each time it is called. Is this the preferred method of work? I get they will be destroyed once the scope is gone but it still seems like a lot of calls to create new Objects when presumably as long as the game is going, those objects stay necessary. My first instinct would have been to simply save the objects in the struct instance as well and only call .show() on each when calling .show() on the struct instance, moving them whenever .set_pos() is called. Is that unperformant and so it is better to always create and destroy objects already at their destination?

Just wondering for some context, thanks for any insights.

[corwinkuiper]

You can do it either way, whatever you find easier. The approach used in the book is what we use in our more recent games having taken everything we've learnt. Creating and dropping an Object is always cheap.

[Mambouna]

Thanks, good to know. Then I'll stick with that as well.