rpi-rgb-led-matrix VS zig

Hzeller - https://github.com/hzeller/rpi-rgb-led-matrix/blob/a93acf26990ad6794184ed8c9487ab2a5c39cd28/bindings/python/README.md

I installed https://github.com/hzeller/rpi-rgb-led-matrix

Anyway I used this library on a Raspberry Pi Zero https://github.com/hzeller/rpi-rgb-led-matrix I only displayed static images but the "image-example" shows how to handle animated gifs.

Adafruit makes a hat that you can plug right onto the GPIO port. I'm using rpi-rgb-led-matrix, I also have a guide you can watch on YT here https://www.youtube.com/watch?v=ssyTWpVEl0E

Use a rgb matrix hat, a raspberry pi, and this library.

To control the matrix, a loop is ran and inside things are displayed to the matrix. (I'm using this library https://github.com/hzeller/rpi-rgb-led-matrix)

I found this https://github.com/hzeller/rpi-rgb-led-matrix, this provides python scripts. Please read through them, and then ask specific questions at each step. If python just looks like gobldegock, I suggest you go through some basic python tutorials docs.python.org has a tutorial page, and no you don't have to complete the whole think just read everything about built-ins and basic syntax (for, if, def, else, etc).

If you then follow this forward to the code they originally forked theirs from from (here) and scroll down a fair way you find the entry Improving Flicker that states (in part):

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community