I can relate to this so much. I have started like 3 game engine projects. All of them were as you said: the worked, but they were too ambitious and I was never happy. What I realized is that as a single person it made no sense to make a general purpose library. However, it taught me two alternatives to general purpose projects.
Projects with a scope limited by function. From the last game engine project I recycled the lighting module and turned it into a separate library; now it has more attention and recognition in GitHub that my own engine would ever have.
Projects with a scope limited by goal. I also started a new engine, but this time with a specific game in mind (a 2D platformer, to be exact). This let me decide what features make it into the engine by the criteria of "will I use it in my game?". No more headaches with infinite features to implement.
It is definitely not good to be unrealistically ambitious, but it's also true that if it weren't for that, I wouldn't have learnt enough to get to my current (and future) projects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can relate to this so much. I have started like 3 game engine projects. All of them were as you said: the worked, but they were too ambitious and I was never happy. What I realized is that as a single person it made no sense to make a general purpose library. However, it taught me two alternatives to general purpose projects.