Game devs rely on loops, web devs build state frameworks for sign-ups
Description
The image is a dark-mode Twitter screenshot. At the top, a blurred profile photo and the handle “Saman Bemel Benrud @samanbb · Feb 19” are displayed in white text. The tweet body reads, line-for-line: “Game developers: with enough if statements and while loops I can do literally anything. Web developers: I will use graph theory and a hand crafted functional state management framework to create this sign up form.” Beneath the tweet are typical Twitter icons showing 72 replies, 1.5 K retweets, and 8.7 K likes. Visually simple, the meme humorously contrasts minimalist imperative coding in game development with the perceived over-engineering of modern web stacks, poking fun at state-management libraries, functional paradigms, and graph-theory-inspired frameworks that engineers sometimes deploy for even trivial UI tasks
Comments
10Comment deleted
Game dev: “Give me a delta-time and a while(true) and I’ll build a universe.” Web dev: “Cool - I’ll just topologically sort my React components so the CRDT-backed email field stays in sync with the GraphQL cache during onBlur.”
Game devs ship 60fps physics simulations with 10,000 interacting objects using nested loops. Meanwhile, I just spent three sprints debating whether our email validation should be a pure function or a custom hook
This perfectly captures the eternal divide: game devs shipping AAA titles with nested if-statements deeper than their call stacks, while web devs are three PRs into implementing a Redux-Observable-RxJS-Recoil hybrid just to toggle a modal. Both approaches work, but only one requires a PhD in category theory to understand the signup flow. The real irony? The game dev's 'spaghetti' ships on time, while the web dev's 'clean architecture' is still in the spike phase when the startup runs out of runway
Game devs: two loops and a lookup table. Web devs: a DAG of reducers and a saga so the signup checkbox can reach consensus
Game devs prove Turing completeness with loops; web devs need a full GraphQL schema just to onboard a user
Only on the web can a two-field form justify a DAG scheduler and a bespoke ‘pure’ state manager - meanwhile the game dev shipped 60fps last week with three ifs, one while, and no package.json
So not fair, you swapped them! Comment deleted
So, it is vice verse ? Comment deleted
So true 😂 Comment deleted
yandere dev has logged in Comment deleted