It’s beautiful

“The default is hunter gatherer” kind of leaves out a lot of communal living that happened throughout human history. Someone had to hunt, someone had to watch the kids, someone had to garden, eventually people needed to work on sewage lines and waste disposal.

Nothing about everyone having their needs met precludes the dirty work getting done - heck, some people even enjoy it!

The idea that everyone would just give up taking care of the necessities is, imo, ridiculous. It smacks of the tired line of “in an emergency, it’s every man for himself and no one will have your back” when history has shown again and again that communities come together and mutual aid flourishes in the face of disaster.

I get that feeling, and I’ll echo my sibling comment: I’d much rather read your stream of thought and get on that brain train with you than see some fluffed up and sterilized version.

I also think that having that authentic voice, while it does open us up to criticism and maybe being misunderstood, also gives us a way to receive actionable feedback to improve.

I think we all want to be understood, and for me part of that understanding is seeing the person. How you write is a part of who you are, and I hope you don’t feel like you need to suppress that.

A rather simple game engine to look at is Love2D - I know you wanted 3D, but my main experience is over there. Really, the gist of an engine will be about the same either way.

An engine mostly handles a few basic things like device input, managing the screen (with niceties for things like buffers, sprite maps, etc), drawing, and sound.

Slightly more game-oriented are things like managing the game loop, having an update timer, or calculating collision detection.

3D engines quickly help to smooth out the frustration that is working in 3D in general - lighting, cameras, etc.

As someone else said in another reply: if you want to make a game, see if there’s an engine that works for you. If you want to make an engine, or have very specific needs that require the flexibility and optimization of a custom engine, do that.

I don’t actually see any good points against pagination in the opening, and I don’t see any reason to compare pagination to infinite scroll - in fact, I’d argue that comparing them means there’s a misunderstanding of the problem you’re solving for if you see them as equally viable options.

Imo, infinite scroll is for when you don’t care about ever finding something more than once while scrolling - instagram and TikTok are prime examples of this.

Pagination is the opposite - you have a set of data you want to be able to reliably navigate.

The bit about pagination taking up precious screen real-estate is silly, especially in light of the IS example having a whole search bar (I’m assuming the paginated example has an implied search bar but it’s not mentioned). Pagination doesn’t need to take up much space at all - whether your choice of pagination implementation is good for UX is a different beast.