Since 2023, I have been a dedicated user of Julian's Editor (JE), a platform that has fostered my creativity and allowed me to bring my game development ideas to life. I am not alone in my admiration for JE. Many in our community have grown to rely on its unique features and user-friendly interface. For countless creators, including myself, JE has become an invaluable tool, providing us the means to develop and share our games with the world. However, recent announcements have revealed a troubling future for JE.

The developers of Julian's Editor have decided to merge the Western version with its Chinese counterpart under the new platform, Builda. This decision is poised to not only disrupt the creative flow of countless Western game developers but also lead to the loss of games built on the current JE platform. The integration of these platforms could result in a drastic shift that does not align with the needs and expectations of the existing JE community.

Considering the implications, it is evident that the unique identity and community fostered by Julian's Editor deserve preservation. The prospect of losing games that were built with passion and dedication is disheartening, and it raises a crucial question about the protection and continuity of our digital creativity.

Even the new name, “Builda,” highlights the problem. It is not only generic and already in use by a construction app, but it was also chosen without input from the very community that built Julian’s Editor. A name should reflect identity, history, and creativity—not feel like a machine‑generated label. By discarding the name Julian’s Editor, the merger risks erasing years of recognition and replacing it with something bland and confusing. Our community deserves better.  

We urge the developers to halt the merger and explore alternative solutions that safeguard the existing JE ecosystem. Potential options include updating the existing JE framework independently of Builda, or better yet, maintaining both versions concurrently as separate, thriving entities.

For the developers of Julian's Editor, we ask that you consider the impact of this decision on your community and the legacy of hard work and creativity it represents. We are not against change, but rather advocating for the best path forward for all users. A path that respects and retains what has been built together.

Please help us protect the future of Julian's Editor and the countless projects it houses by signing this petition. Together, we can make our voices heard and influence a decision in favor of preserving what we all hold dear.