Updates of Version 25r01

[CiroZDP]

NEWS (2/25/2025):

I'm confident we can archieve something related with GLFW before this month ends

NEWS (2/28/2025):

Nuh uh. Not so confident now. There's no easy way to temporary blocking Github Actions. And many versions will just fail. We are about to have a mega strike of failing workflows but it doesn't matters. I will notify if I archieved something in a particular platform.

[CiroZDP]

NEWS (3/09/2025):

Ok. Apparently the Linux workflow will take a little bit longer because I can't spot where's the problem.

[CiroZDP]

NEWS (3/24/2025):

Yesterday, I finally solved the GLFW issue on Linux. I had been struggling with it for 15 days. It was awful because I didn’t have the courage to install WSL. Yesterday, I finally installed it, and it helped me a lot.

Now, I’m not sure what to do next. GLFW is (mostly) working fine, and MS-DOS is still running on the null framework. Because of that, I’ll probably continue GLFW development in MS-DOS.

However, I’m a bit concerned about working with such an old architecture. DJGPP, for instance, is quite uncomfortable to use—you can’t properly link libraries, so it’s often better to compile a raw C file directly within the game’s compilation process.

I feel the same way about GLFW. Sooner or later, I’ll have to replace it with something else because it doesn’t fully support the naming conventions I typically use. This could make it difficult to integrate both things, as I like using abstractions. While GLFW is quite complete, at some point, I might end up creating an abstraction that is twice as hard to maintain, worse than GLFW, and much less understandable for most people. So, at least for now, and probably for a long time, I won’t worry about it—until it truly becomes a problem.