> These two points from both of your comments don't really reconcile (today). I didn't write both comments btw, the parent comment who I replied to is someone

> These two points from both of your comments don't really reconcile (today). I didn't write both comments btw, the parent comment who I replied to is someone else who mentioned the environment. > Sure, if you're optimizing for "profits tens of millions of dollars a year" then go ahead and spend/receive as much money as you can and disregard all else, like the environment, employees health and so on. It's possible to be environmentally friendly, have reasonable server costs for an app built with Python / Ruby / PHP, keep employees happy and make major progress towards improving Earth. The place I work at is focused on clean energy management and the environment. It's a privately owned company so it's not my place to share any numbers but I can say we don't throw money at problems as a first line of action. For context, the company has been around for over 10+ years and uses PHP (public info based on HTTP headers). I joined a few months ago as a full time employee after spending ~20 years being a solo developer doing contract work. I hope that sets the stage for how much I like the folks working there and how they run things. Also for context, I don't actively write PHP there. My role is focused on deploying their app(s) although I have developed some Python based services for them (I did contract work with them for a while before joining full time).