Have a look here. Did you not search for the answer? That's part of the Arch(based) ethos. We tend to like to learn by reading whatever is required. :). Source: about 1 year ago

I was also looking for something nicer for Arch, but haven't found anything as nice as Nala. For now, I switched to pikaur, which at least displays updates in a much clearer way. Source: almost 2 years ago

Nice, but this definately needs a dependency resolver, otherwise it can only install a fraction of the available AUR packages. Since you're already using python, you may adapt your whole code on top a another python-based AUR helper like pikaur. You maybe also could take at the dep resolver of my ABS project. It's python, too, maybe not as clean as pikaur's code but simpler and not too integrated. Source: over 2 years ago

I've been using pikaur ever since pacaur became abandonware and I'm very happy with it, can't recommend it enough. Sure, it's not implemented in Rust or Go so it's certainly not as cool as yay or paru but that doesn't really matter much to me, being an end user. I don't really care as long as it does its job, as advertised. Source: about 3 years ago

I also read that Salt was using MessagePack to format their messages. MessagePack is a format like JSON, but more compact. - Source: dev.to / 9 months ago

So appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls? Source: over 1 year ago

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. Source: over 1 year ago

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. - Source: dev.to / over 1 year ago

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. Source: almost 2 years ago