Kingdaro there is no sensible argument that you can make which would lead any reasonable human being to believe that if they are working on a game engine, even if it doesn't innovate anything, that they should stop and work on a game.
And I never implied for anyone to simply drop work on their engines. I just stated that, in my eyes, working on games is much more important than working on game engines.
And they also come in handy if you ever do actually want to make a game.
This is where the problem lies. The reasoning behind my massive two page rant was that, if you actually do want to make a game, to not focus on the engine, but to actually make the game. When creating a game, you should focus more on the game itself more than the inner workings and architecture of the game, and I feel like creating your engine distracts from this.
Game Engine's are great for making for learning about rendering, physics, optimization, etc. Not only are they fun projects but they are extremely educational. Every time I've made an engine I have come away a little smarter.
I agree, like I stated above. There's no problem with making an engine as a hobby and/or 'just to do it', but at the same time, there's no good reason to expect anything to come out of it, other than the experience of making the engine. If that's all you're doing it for, then fine, I guess, but I personally wouldn't waste my time without an actual game coming out of it.
While it is nice making games, there is no reason why it is more important to make games over game engines.
As a person who really loves game development and a passion for video games, I cannot see how the creation of a game engine would be any more important than a game. For those more technologically minded, how a game works will be more important than the game itself, but in the perspective of
game development, which is, by the way, the process through which
games are made, making an engine beforehand is a waste of time.
