4 ms·
It kinda sounds like martyrdom, or a monk or philosopher, pursuing enlightenment or, in this case, knowledge and expertise. But like with any software developm
by Cthulhu_ 3y ago
It kinda sounds like martyrdom, or a monk or philosopher, pursuing enlightenment or, in this case, knowledge and expertise.
But like with any software development, technological self-gratification doesn't make a product. Every programmer loves writing code, but you need to be aware whether you're writing code for writing's sake or if it has an objective.
If you want to develop games, develop games; focus on results first, only when you've proven to yourself that it's games you want to develop instead of the technology behind them can you start to think about what the existing engines are lacking that your custom engine would do better.
It has the same energy as PHP developers from a decade ago that for some reason all insisted on writing their own frameworks, CMSes, etc.
- whateveracct 3y agoRight exactly I'm not trying to be an efficient gamedev pumping out money making products. I have my boring software career to make me money. I am seeking higher satisfaction at this point in my life.
- johnnyanmac 3y agoYou make your own tech in part because current tech doesn't satisfy your needs. One huge weakness of the popular 3rd party engines is iteration times. The author alluded to such. When you get to a point where a few lines of code takes 5 minutes to compile so you can test a small tweak, you quickly lose your motivation. So I get it. These engines are made to help medium-large scale studios create high profile games, collaborated on by dozens, hundreds over a few years. An single dev doesn't need all that tech but it's tech that bloats down their iteration cycles. Especially if your goals are a small 2D game.