Unity's recent controversy has reignited discussions about game engines, with some advocating for switching and others highlighting the significant time investment required. This has led to renewed interest in building custom game engines. The author, who has been developing their own engine for three years, offers insights into why one might embark on such a journey.

Reasons for creating a custom engine include freedom from "questionable corporate decisions," cost-effectiveness (excluding development time), and the ability to optimize for specific needs like performance, iteration speed, and architecture (e.g., using ECS for games with millions of objects). It also grants full control over internal workings and technology, allows the use of preferred programming languages, and can result in smaller distribution sizes. Furthermore, it offers a unique learning experience, fostering a deeper understanding of game development and other engines. The author emphasizes personal enjoyment in coding and problem-solving as key motivators.

However, building an engine is a demanding and time-consuming endeavor, unlikely to rival industrial engines like Unreal without considerable resources. It can lead to a focus on engine development over game creation, potentially causing burnout. The author concludes that if the goal is to make a game quickly, an existing engine is advisable. For those seeking growth as developers and possessing ample time, building an engine can be a rewarding, albeit challenging, path.