sorry if I reopen a contentious topic.
I believe some possibilities weren’t brought up in the last discussion.
rbfx adds neat features/changes to Urho : the lightmapper, automatic bindings via swig (C# for now, but lua should be relatively easy to add), built-in serialization, better containers, …
But some people want to :
- avoid the C# ecosystem (because Microsoft)
- keep angelscript (which is removed in rbfx, and would need work to add to swig definitions)
- keep the original editor (built on angelscript)
- avoid the eastl containers (because EA)
Here’s my take on it :
so long as the engine itself doesn’t depend on C#, the binding does no harm.
I don’t like Microsoft either, but the language is good for scripting purposes and is becoming the industry standard. If Microsoft fuckery happens, we just keep the last clean open-source version of the .Net environment until the userbase has migrated their projects, then ditch the binding
while angelscript can’t have auto bindings, we could keep the original angelscript manual bindings (@rku : can you confirm that the manual bindings could be brought back ?). Also, let’s drop the burden of maintaining them to whoever uses them instead of those that add features.
thus, the original editor can be kept with angelscript for the sake of retro-compatibility, but having the editor dependent on one of the scripting languages was a really bad idea. The new editor already in rbfx, while not full-featured, is in c++ like the rest of the engine as it should, on top of being easier on the eyes. Let’s just build it up to what the old one was capable of.
the eastl containers are different from the C# bindings in that they are an integral part of the engine. BUT a container library is very different from a language. Even if it goes closed-source or stops being maintained, we would just keep the last clean open-source version and maintain it ourselves, which is already the case with the actual containers anyway.
Hope that makes sense, looking forward to your responses,
and thanks for coming to my TED talk