mlb-led-scoreboard VS crystal

So this is the instructions for the scoreboard: https://github.com/MLB-LED-Scoreboard/mlb-led-scoreboard/wiki

First and foremost, thank you to Tommy Farley’s MLB LED Scoreboard Project for the inspiration + most of the code base. My brother and I have been wanting a CFB equivalent of this forever, so we decided to build our own using a Raspberry Pi Zero and a 32 * 64 LED Matrix. Here is a link to the video demo. If you just so happen to have the same equipment, great! Here is our GitHub repository with the code + instructions on making your own. We’re also looking to sell these in the future (once the semiconductor shortage has hopefully settled down)— if you’re interested please let us know! As always, feedback from you all is great appreciated on how we can make this better.

About $200 in parts, runs out of a Pi.

I help maintain the MLB LED scoreboard project and we don't recommend anything less than 5A for a single matrix, and you're running 6 of them. In fact, the tutorial you linked suggests that you are way underpowering your matrices: https://learn.adafruit.com/32x16-32x32-rgb-led-matrix/powering

quick paste of an old how to file i made however heres the github link gh

I bought the RGB matrix and Raspberry Pi and assembled it. Just followed the process here to get the software running - https://github.com/MLB-LED-Scoreboard/mlb-led-scoreboard

You can look at the code/follow steps to build one yourself here: https://github.com/MLB-LED-Scoreboard/mlb-led-scoreboard. It's pretty straight forward if you have a technical background but if not it might take you a bit to get up to speed with the raspberry pi.

It supports a bunch of different matrix sizes, requires no assembly, and is free, so developers of software like the MLB LED scoreboard don't have to set up and maintain physical hardware to maintain the project. Consumers of those types of projects get the same benefits so you can run the emulated version without needing to pick up a soldering iron.

27. Crystal - $77,104

I like the first code example on https://crystal-lang.org

    # A very basic HTTP server

Obviously as an interpreted language, it's never going to be as fast as something like C, Rust, or Go. Traditionally the ruby maintainers have not designed or optimized for pure speed, but that is changing, and the language is definitely faster these days compared to a decade ago.

If you like the ruby syntax/language but want the speed of a compiled language, it's also worth checking out Crystal[^1]. It's mostly ruby-like in syntax, style, and developer ergonomics.[^2] Although it's an entirely different language. Also a tiny community.

[1]: https://crystal-lang.org/

Crystal is a nice language that's not only simple to read and write but performs very well too. And the documentation is amazing as well.

Ruby is a super fun scripting language. I much prefer it to python when I need something with a little more "ooomph" than bash. It's just...nice...to write in. Ruby performance has come a long way in the last decade as well. There's libraries for pretty much everything.

My modern programming toolkit is basically golang + ruby + bash and I am never left wanting.

I do find Crystal (https://crystal-lang.org/) really interesting and am hoping it has its own "ruby on rails" moment that helps the language reach a tipping point in popularity. All the beauty of ruby with all of the speed of Go (and then some, it often compares favorably to languages like rust in benchmarks).