Should probably rewrite it in rust, to solve the markets memory leaks, otherwise everything will keep going up.
But asides from the securities offered by the typing system and borrow checker, Rust (and Go; and maybe others to some extend) have going for them is that the compiled binary is "OOTB".
I'm on ubuntu, and it seems all python tooling is there to start running Gamestonks Terminal. But more often then not, getting a Python, Nodejs or Ruby project running requires a lot of fiddling, insider-information (what is npx, why did pipenv just break my entire desktop, why is this 'rbenv' thing giving these weird 'RVM' errors?).
A rust project: download it, unzip it, run it. A very short Daft Punk song, really.
See what I did? It’s an older meme, but it checks out.
But all of these don't make the packaging easier, they merely move the complexity of such setups from "all users" to "the devs". Which helps a lot.
But it's still easier if no-one has to deal with this.
The c implementation didn't hit the point of me being able to endorse it before I just gave up and let people use Less if that's what they prefer.
Runtimes, man. They can be the pits.
This implies that markets going up is a problem that needs to be solved.