This helps highlights the main issue I have with python today, and that's running python apps.
Having to ship a compiler to a host|container to build python with pyenv, needing all kinds of development headers like libffi for poetry. The hoopla around poetry init (or pipenv's equivalent) to get a deterministic result of the environment and all packages. Or you use requirements files, and don't get deterministic results.
Or you use effectively an entire operating system on top of your OS to use a conda derivative.
And we still haven't executed a lick of python.
Then there's the rigmarole around getting one of these environments to play nice with cron, having to manipulate your PATH so you can manipulate your PATH further to make the call.
It's really gotten me started questioning assumptions on what language "quick wins" should be written in.
HFT also still pays top dollar for competent FPGA developers. I'd wager they're willing to pay more than the listed industries too, especially if you factor in profit sharing and bonus structures.
This doesn't address the issue, as that still leaves the vulnerable git binary on your system. It just takes one call to /usr/bin/git instead of /usr/local/bin/git to fall victim.
I've seen those issues as well. I it Duet more as a second display more on my win8.1 laptop, and have very strange 'disconnects' - the iPad screen just randomly goes berserk and technicolor, and I have to quit the app and restart to get it picked up. This usually happens around the same times iTunes tells me there's an update, so guessing it's related.