OP wants to build a game. When I build games, I start high level (Python, Lua, GDScript, etc), then move the slow, stable bits to something faster. That’s a really effective flow, and at the end, I get a great scripting interface for my game.
But then, given the complaints, I’m not actually sure they do want to build a game, I think they really want to build a language, and maybe an engine.
… I start high level (Python, Lua, GDScript, etc), then move the slow, stable bits to something faster. That’s a really effective flow, and at the end, I get a great scripting interface for my game.
That’s the way to do it. “Premature optimization being the root of all evil” and all. Something that is slow but works is always better than something fast that doesn’t.”
But then, given the complaints, I’m not actually sure they do want to build a game, I think they really want to build a language, and maybe an engine.
And there’s nothing wrong with that. I personally find no interest in programming for programming’s sake. I need a problem to solve first. But what if I don’t have a problem to solve? Create one! Generating a problem is a valid way to let myself “enjoy” the combined agony/pleasure of programming.
Agreed, it’s just nice to know that going in to a massive article like this. Are these reasonable complaints, or are they just justifying a new project for themselves?
OP wants to build a game. When I build games, I start high level (Python, Lua, GDScript, etc), then move the slow, stable bits to something faster. That’s a really effective flow, and at the end, I get a great scripting interface for my game.
But then, given the complaints, I’m not actually sure they do want to build a game, I think they really want to build a language, and maybe an engine.
Agreed, it’s just nice to know that going in to a massive article like this. Are these reasonable complaints, or are they just justifying a new project for themselves?