In the last years I've been asked multiple times about the comparison between raylib and SDL libraries. Unfortunately, my experience with SDL was quite limited so I couldn't provide a good comparison. In the last two years I've learned about SDL and used it to teach at University so I feel that now I can provide a good comparison between both.
Hope it helps future users to better understand this two libraries internals and functionality.
It all happened when I decided to run Geekbench 5 on my phone: surprisingly the single-core performance matched my 'old'¹ Pentium T3200 and surpassed it in multicore. Since I've been having fun with distcc for the last few days, I asked myself: 'Can my phone really help my old laptop build faster? nah, hard to believe... but let's try'.
Without further ado: YES. Not only can my phone be faster, but it can significantly help in the build process, I believe the results below speak for themselves:
Building Git (#30cc8d0) on a Pentium T3200, 8m30s
| // | |
| // Lookup Tables for Transvoxel's Modified Marching Cubes | |
| // | |
| // Unlike the original paper (Marching Cubes: A High Resolution 3D Surface Construction Algorithm), these tables guarantee | |
| // a closed mesh "whose connected components are continuous and free of holes." | |
| // | |
| // Rotations are prioritised over inversions so that 3 of the 6 cases containing ambiguous faces are never added. 3 extra | |
| // cases are added as a post-process, overriding inverses through custom-build rotations to eliminate the rest. | |
| // | |
| // Uses the exact same co-ordinate system as https://gist.github.com/dwilliamson/c041e3454a713e58baf6e4f8e5fffecd |
This git include a list of programs, tools, engines and libraries free and open source intended to make videogames.
NOTE: This gist is a support material for the talk "Open Source and Videogames" given by me, Ramon Santamaria, on October 26th 2021 in Canòdrom, Barcelona. All the materials listed here were explained in detail in a +2 hours talk.
This is an outline of what I'm looking for in a game engine.
The entire engine should be implemented as a single file library. The user of the engine should be able to download the source file, add it to their source tree, and go.
The engine needs to have a simple build system. You should be able to compile the engine with something like
gcc my_game.c -o my_game -lpthread -lm -ldl, and on Windows gcc my_game.c -o my_game.exe. Only libraries that
come standard with the compiler should be allowed. The engine should also be built in C89 so it Just Works across
all compilers.
| // the donut code with fixed-point arithmetic; no sines, cosines, square roots, or anything. | |
| // a1k0n 2020 | |
| #include <stdio.h> | |
| #include <string.h> | |
| #include <unistd.h> | |
| #define R(mul,shift,x,y) \ | |
| _=x; \ | |
| x -= mul*y>>shift; \ |
We did it! We broke gist.github.com ;) So head over to the new home! Thank you all!
2021.10.20: https://github.com/AveYo/MediaCreationTool.bat now open for interaction
Not just an Universal MediaCreationTool wrapper script with ingenious support for business editions,
A powerful yet simple windows 10 / 11 deployment automation tool as well!
