@TimSweeneyEpic for Christmas, can you reconsider the Epic EULA clause g?
There are mutually beneficial and fair ways to achieve your goal of ensuring future viability without blocking use case agnostic tools that would directly benefit UE devs.
๐ ๐๐
@yeetyeetusyeet@TimSweeneyEpic How can you talk about developer freedom when you've actively gone out of your way to kill C# in UE for years. You don't want developers to be able to make their own decisions about what tool is best for the job? clause G of the EULA is a disgrace to developers.
@jimofl @migueldeicaza@stroughtonsmith We agree with this 100%. We were just told no by Epic this month; help us with your voice, they should know it's ok to be fair, grow, and have integrity: https://t.co/jE3kL1YC18
@migueldeicaza@stroughtonsmith Joining the conversation late with our own https://t.co/944p62QxLy tool which adds C# to UE.
We've created a petition in hopes of having Epic reconsider on behalf of their community: https://t.co/jE3kL1YC18
Please sign this petition letting @EpicGames know you'd like to see Code Orchestra distributed for Unreal Engine under fair rules.
https://t.co/zjPS027dz0
"we updated the UE4 EULA to require redistributed programming language integrations to be free and open source, so that if one gained a critical mass in popularity, Epic could adopt it and ensure its future viability" - unidirectional benefit for Epic
"when an engine is written in C++ and gameplay is scripted in another language, the interoperability barrier between languages eventually grows overwhelming." - we hope our videos have fully proven otherwise. Our novel approach to the problem fully solves for this.
We hope Epic truly reconsiders this stance someday. Many are ready and willing to adopt UE given a solid and well supported product would be available.
https://t.co/fhf9wL0xlB