The statement that making games is easy implies games in general, not "my first game" type games. Without significant qualification, the statement is no more true than saying "coding is easy." You have to engage in some serious logical gymnastics to justify it.
Likewise, it seems fruitless to argue over a general qualifier when the poster already clearly said they have a different definition. Better to spend more time aligning than talking past each other.
I'm not sure what exact action you're suggesting I should have taken. If you're objecting to my tone, well it's too late for that. I've spent a lot of my life hearing developers glibly dismiss the importance, complexity, and difficulty of most non-coding jobs. I'm not interested in holding a neverending stream of hands while developers embark on their journey to discover that other people's contributions and expertise are consequential. Sometimes people who don't know what they're taking about just need to hear the right answer.
>people who don't know what they're taking about just need to hear the right answer.
If that's your response to my statement, all I can say is: you're not owed an audience and your tone is a great way to have people ignore what may or may not be "the right answer".
But no, ironically enough you're proving my point. I'm simply saying to clarify what's on the users mind before going on a rant about what you assume they mean. There's no point in arguing about an aquatic fowl's eating when the user was talking about DuckDuckGo. And then doubling down by saying "but it's true ducks eat too much bread". At this point It's clear your conversation is a tangent no one is interested in taking.
