CRYENGINE VS Cocos2d

False. See for yourself. They openly state that you can "Use CRYENGINE for free. 5% royalty applies when you ship your project. Your first $5K annual revenue per project is royalty-free.".

yeah, I think you're right there. I know the feeling of being on the other side of the problem, so I can relate with the crytek guys. they need to get their shit together, sure, but they are human beings and these problems are really hard. I mean, head over to github, there's a version of the cryengine there for you to read and comprehend if you like. check out the collision detection :)

I'd wager that somewhere around 99% of games for sale on Steam from large shops to small indie games are either created with Unity, Unreal Engine, or CryEngine (Amazon's Lumberyard is a close relative of CryEngine).

I have very high hopes for Godot. Besides, if you're the sole developer of a side project, you don't want to use what the AAA titles use. Have you seen the length of the credits on those things? If that's the path you want to go down, then you might as well give the cryengine a go, get yourself a license to some mocap software, etc lol

Unreal Engine, Valve Source Engine, Crytec, and Unity are the big ones. I suspect that’s what people mean when they say this. There are a few others, but they are either used in less popular games, or they are proprietary engines that are not publicly available like the Snowdrop Engine. I know some PC games would ship with the editor too, although it’s been a long time since I’ve done any mod work, so I don’t know if that’s still the case.

The proprietary options of Unity, GameMaker Studio 2, Unreal Engine, and CRYENGINE.

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.