Allegro VS Cocos2d

Allegro (zlib/plain C) https://github.com/liballeg/allegro5

Some nutjob has taken control of https://liballeg.org to redirect it to some anti-Nazi page that mentions Kotaku, comparing them to nazis.

C, C++, Allegro, SDL, Some rudimentary SQL, Some basic BSD Sockets. But I also took some time to learn 3D math, trigonometry and linear algebra so I can include some basic 3D examples in my portfolio. I was later told that it was the 3D math that made the difference because if I (barely finished HS) can do that I can probably learn everything they give me.

Wow, DJGPP and Allegro (still going!), that takes me back - that and Bloodshed IDE were my weapons of choice back then!

liballeg.org

allegro 5 is quite alright with fonts

allegro5 is a great rendering library if you want to get something 2D on the screen fast

Hell, their website says in the first few sentences it isn't an engine.

A while ago I was getting started with the Allegro5 game engine (+Rust bindings). It's the same engine used for Factorio. I wrote a simple egui-integration to have nicer UI options. It was mostly for myself and is thus poorly documented but maybe you get some ideas how to make it work.

Here's a simple program using Allegro

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.