News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by jon_richards on Wednesday October 18, 2017 @08:28AM (#15498540)
For a number of reasons, I haven't bothered to do a complex build/deploy process. I write in python, I freeze the requirements into requirements.txt, and I type "eb deploy". Anything else is overkill for me.
Re:Why we switched from Python to Go by dozzie on Wednesday October 18, 2017 @08:52AM (#15498697)
And then you have different lists of installed packages in your development environment and in the production and even between two different production servers (which can silently and/or subtly break your software), and you need to manually install all the C/C++ libraries and compilers and non-Python tools and whatnot, and the upgrade process takes a lot of time and can break on problems with PyPI and/or packages that went missing, and you can't even sensibly downgrade your software to an earlier version.

Yes, avoiding learning how to properly package and deploy your software is totally worth this cost.

Re:Why we switched from Python to Go by hasenj on Wednesday October 18, 2017 @11:19PM (#15505242)
Python does not really have a "build" step. _That_ is the problem.

I think Heroku also played a role in prolifirating the idea that you can just push your code (from a git repo) to a server, and the server will take care of deploying it. Which usually means the server will install all the dependencies from pip during the process.