I was more making the point that starting by building an engine is a huge commitment and you need the skills and times (and the reason) to do that.
> So yeah, it's not "that hard" if you use a product which has already had millions of developer hours put into it like Unity or UnrealEngine.
What point are you making? The GGP correctly claimed it's "not hard" for small teams to make games. The games they referenced were made by small teams. The fact those games used an off the shelf game engine is immaterial. There's no "point" to make about it.
Your "point" comes off as a qualitative judgement about those developers using an off the shelf engine. If you've got no problem with someone using Unity what point are you really making?
Using someone else's hard work doesn't mean that its easy, just that you don't have to do that work yourself because others have done it for you.
> Your "point" comes off as a qualitative judgement about those developers using an off the shelf engine.
I didn't read it like that at all. In most cases, for most teams (certainly small ones), using an off the shelf engine is absolutely the right call, exactly because it means you don't have to solve the hard graphics problems yourself. But using an off the shelf engine does not mean that those hard problems don't exist or aren't hard, just that you can outsource them to the engine vendor.
From the point of view of a game developer, having good graphics is "easy" because Unity and Unreal exist. The fact Unreal and Unity exist enables thousands of developers to make games that couldn't otherwise. Making a "point" that a small game developer didn't write their entire stack is just shitty gatekeeping.
But this is not what the article, and this comment section, is about.
Do you make the same comment about someone using standard libraries or frameworks? How productive would you be without system libraries or even an OS?