Allegro VS MessagePack

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

so appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls?

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing.

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto.

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages.

I'll try that msgpack.org website.

First of all, you're comparing this to GSON and Kryo, how does it compare to Msgpack, fast-serialization, but also Elsa and I'm sure, many others? Are there any limitations and/or trade-offs?

Upvote for msgpack, one of the great undervalued message protocols available.

I have two suggestions Capnproto, MessagePack (those are only the two examples that came to mind first, i bet there are even one or two especially developed for rust). Both of these are better than json in nearly every way.

Encode messages as JSON or MessagePack.