alt Hacker NewsHah. I've been working on my own engine for over a decade, and I completely relate to this. I've torn it down and rebuilt it a few times, I've got multiple branches of it that are built for specific things... but when I want to do something I know it can't do, that could be easily done in some other engine, it just puts a bug up my butt to try and make my own code do that thing. Then I dive into code I haven't looked at for a few years and I realize that so many things could be improved. And I lose a week of sleep yak-shaving this thing that will almost definitely never be seen or used by anybody else. But I see it as a kind of craftsmanship and sharpening my own tools. I don't know another, better way to do that.
Replies
>I've been working on my own engine for over a decade
Username checks out
> But I see it as a kind of craftsmanship and sharpening my own tools. I don't know another, better way to do that.
Toooootalllly. This project started out for me as a learning exercise, and for a long time an explicit non-goal of the project was to ship a game. It's just my own little land that I know every nook and cranny of for experimenting and, sharpening my tools, as it were. It's also the best way I've ever found.