Allegro VS libuv

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

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Libuv, the C library that gives Node.js its asynchronous, non-blocking I/O capability is responsible for managing the thread pool. Node.js gives you the capability of using additional threads for computationally expensive and long-lasting operations to avoid blocking the event loop.

Node.js is written in C, C++, and JavaScript. The core components of Node.js - the V8 engine and the libuv library - are written in C++ and C, respectively, since these languages provide low-level access to system resources, making them well-suited for building high-performance and efficient applications. JavaScript is mainly used to write the application logic.

x8 apparently https://github.com/libuv/libuv/pull/3952

Notably upgrades to libuv 1.45 which has io_uring support. Faster file system access! Awhh yeah, it's on.

Remarkable what a mild & unintrusive PR adding io_uring was. https://github.com/libuv/libuv/pull/3952

Well, the single-threaded nature ultimately leads to its biggest downfall. Node.js utilizes a synchronous event loop engineered using Libuv that takes in code from the call stack and executes it.