Arcade VS Cocos2d

I work on a Python game engine called Arcade[1] and other projects within it's Github organization such as pytiled-parser. We also help to drive continued development and improvement within Pyglet[2]. Recently, my efforts have been focused on creating a version which can be run in web browsers by using Pyodide and WebGL[3], though that is still fairly early stages.

Arcade's primary focus is on being an educational tool for beginner programmers, so my hope is that with browser compatibility we can lower the barrier to entry further and make it more accessible and easy to get started with. In a similar vein to the goals of browser compatibility, we've recently enabled full compatibility with Raspberry Pi through the use of OpenGL ES(and this was largely only possible thanks to the huge amount of work that everyone involved in the Mesa project puts in)

I'm not the original author of Arcade, but I am a current maintainer and put a substantial amount of time into it and it's community.

[1] - https://github.com/pythonarcade/arcade

Interesting, looks like some of the default fonts are not getting frozen as part of the executable? I opened an issue: https://github.com/pythonarcade/arcade/issues/1252

Website: https://arcade.academy

Create a game! Get some ideas here: https://arcade.academy

You can look at the example code and tutorials here: https://arcade.academy/

Added clear method to UIManager (#1116)

Arcade can now run in headless mode on linux servers opening more possibilities for users in for example the data science community (#1107). See Headless Arcade for more information.

Fixed issue #978, copy button in examples moved to the left to prevent it disappearing.

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.