Re:Releasing the Unity C# source code
by andrewmcwatters on Monday March 26, 2018 @12:11PM
(#16679931)
This eerily reminds me of how Valve Corporation handled the now abandoned Source engine, and it's 2004, 2007, and 2013 mainline public SDK branches. After this experience, I will absolutely not consider using closed engines. The feeling of putting years of work into a project on a closed engine only to run into issues further down the line that cannot be resolved by proprietary roadblocks caused by the engine's company changing direction instills a burn that you cannot heal from and takes away a sense of innocence on a hobbyist platform.
[ Parent
| on HN ]
Re:Releasing the Unity C# source code
by pheldagryph on Monday March 26, 2018 @02:04PM
(#16681023)
Any suggestions for open engines with some similarity to the tools provided in Unity3d, Lumberyard/Crytek, or Unreal4?
Re:Releasing the Unity C# source code
by digitalether on Monday March 26, 2018 @03:02PM
(#16681512)
Check out Godot! It Looks very promising. I mess around with MonoGame but will look at switching over once they fix some of the bugs with the newly added c# support.