Ugh this specific python module won't work on heroku with gunicorn and I've already wasted 4 hours porting to heroku

So at work, I was trying to convince a senior programmer to adopt Golang for a new project that would need to handle large amount of throughput as oppose to Django with gunicorn and other optimizations (which is what we usually do).

The response was "we'd have a hard maintaining it, as no one really knows Go and it will be hard to hire people with Go knowledge".

So my question: "in your opinion, is that a good reason?" I have some go experience from other jobs, it seems like a superior solution for this problem.

Freaking gunicorn.

Took me over 12 hrs to figure out why issues were happening on staging server and fix them.

You'd think I'd fucking learn by now to check for typos before going off on a tangent of over complicated reasons why something may not be working... Learning python/django for the first time, and have been trying to figure out how to run gunicorn... turns out I was typing myproject.wgsi rather than myproject.wsgi...

Though I suppose not knowing about how python modules work added to my confusion... still... ugh...