Torque3D VS Cocos2d

On a similar note, released games with open sourced code: https://osgameclones.com/?tag=official

https://torque3d.org was used on Airship Dragoon, Marble Blast Gold, Penny Arcade Adventures, Legions: Overdrive and descends from the original Tribes engine.

Hellbreaker, Bit Champs with https://u3d.io

And plenty of successful games with Ogre, including Torchlight: https://www.ogre3d.org/showcase

Torque 2D/3D: Didn't do too much digging around on this one, but both versions are MIT licensed like Godot, but it seems like the project is a little more mature, with built-in multiplayer support. Could be worth looking into as an alternative to Godot if you really want something with MIT licensing.

But from now on, I think I will abandon that, and continue with Torque3D engine : https://torque3d.org/

Torque3D- This one seems great for beginners, as it's free and open-source. The downside is, I'm not sure if it has enough features for complex projects or how secure it is.

Torque3D (the engine used to make Tribes 2, now open-source)

No lie, that overall looks a lot like a game done for a senior design project 15+ years ago using Garage Games' (now https://torque3d.org/) RTS kit.

Torque

That's all I can really tell you from what you've posted. The original version without the Blowfish encryption is open source (eg. https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/scripting/lua-bindings/manual/CCLuaStack.cpp) , and I don't really understand how why you have so much symbol information available if what you're trying to disassemble isn't also probably open source

As others have pointed out, the biggest difference you're seeing is likely due to the _version_ of OpenGL (and hence GLSL) version. That said, there are still important differences. I'd recommend looking at a comparison between the same shader in a project that supports both OpenGL & OpenGLES. For example, here's a shader from cocos2d-x https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/renderer/shaders/positionColor.vert. Note the only difference in this case is the additional precision qualifier (lowp) for v_fragmentColor. Note too how cocos uses preprocessor macros to handle this, so they don't have to maintain separate shader sources. Depending on your goals, you might be interested in tools like Nvidia cg or nvFX that allow for creating shaders in a dialect agnostic way, but ymmv.

Speaking about markdown files on GitHub, I know that there are some repositories that have very stunning README markdown files, such as this one for Cocos2d-x, whcih includes images in conjunction with text. I might do the same for my repository as well. Considering VS Code have an extension for .md files, this might come in handy when I consider using VS Code to contribute to my game projects.