1. Yes and it all does not matter in the slightest for discussing if a language is a right choice for something like Piefed. Not that there’s much to engage with in the original post - I almost regret leaving a comment on a post like this, but I feel this may be a learning for some.
2. There is zero significance in it being supported in “that” way. There used to be a Go-specific runtime (before there were OS runtimes), but they have dropped it because it made no sense once OS runtimes appeared. If you use TS you likely already have a build step somewhere before deployment unless your function is dead simple (which admittedly it should be, but rarely is). Might as well compile a binary, it’s not that complicated. And yes, using a compiled language like go (or C, yes) may absolutely be the correct choice depending on what you need - if it’s in a hot path which serves a lot of traffic then it may lead to much better warm up times and better throughput, as there isn’t a whole runtime to boot and script to interpret like there would be with Node and/or Python (let’s not talk about Java). I’m simplifying a bit, but hope that helps.

I’m just making a case of how not obsolete python is.

There’s no need to do that, it’s self-evident and the original post does not deserve a second of anyone’s time.