speed-comparison VS arl

For example, Java runs on the JVM (Java Virtual Machine) instead of running directly on the hardware, and it also has a garbage collector to handle memory management. Running on a virtual machine means your code is more abstracted: you only have to worry about the JVM and not about the platform you’re running on (since the JVM is the platform), and it’s more portable since your code can go on anything that runs the JVM. But running the JVM as an intermediate layer takes more computing power and so does running garbage collection, meaning that you experience a performance penalty. Here’s one benchmark I could find comparing the use of different programming languages to compute pi, in which Java took about 3x as long as C to complete the same task

Or you've got the speed comparisons (https://github.com/niklas-heer/speed-comparison) -- Python is probably something like 10% the speed of C/C++ (although, like I said, 99% of the time that's comparable to premature optimization).

Looks like a PR was merged yesterday to make the code more simd friendly https://github.com/niklas-heer/speed-comparison/pull/52

Sure, they could have chosen Python. But I doubt the language differences account for even a noticeable percentage of the slowness of Brew.

I think another good approach might be to study some existing VHDL-based open source projects. For example, here is a list of the most-stared VHDL GitHub repositories.