Have you tried writing &quot;a quick little server&quot; in Python and deploying it?<p>Packaging and deployment aren&#x27;t problems in Go OR Python if you&#x27;re only solving trivial problems.<p>With a larger project, you might have an easier time packaging and deploying Go code, but that&#x27;s largely because there are no libraries to package. Admittedly packaging can be a pain in Python, but that&#x27;s usually because of poor choices in dependencies. Packaging Python with a few mature dependencies isn&#x27;t hard in my experience. It&#x27;s the projects where some idiot has pulled in every 0.x versioned library in pip that are hard to package. When Go has as wide a variety of libraries as Python people will run into the same problems in Go.<p>You could argue that at least for now Go doesn&#x27;t allow you to shoot yourself in the foot that way, but I&#x27;d rather have the option.<p>I&#x27;m not defending Python in particular here. I&#x27;d say the same things I&#x27;ve said here about any mature language with extensive libraries.<p>If you&#x27;re espousing Go because of easy packaging and deployment, I strongly suggest that you consider whether that&#x27;s actually a feature Go will have long term, and whether you&#x27;re currently paying for that feature by having no libraries available to you. The only lesson I would take away from Go&#x27;s easy packaging is to only use mature dependencies that pull their weight.