[cassandravoiton]

There are plenty of bench marks showing 10 to 100 times is in the ball part. Computers use masses of power because there are so many of them. As they get more efficient, their numbers increase. The benefit of using faster languages is constant irrespective of the efficiency of the machine on which it is running. How can wasting energy be OK? Even if you don't think it has climate change effects, it has economic and energy security effects - non of them good.

[gdg92989]

I wouldn't say its OK to waste energy but you have to put things in perspective. Your first concern should be to save the users time. The less time they have to use the program to achieve their goal means less instructions. Videos like these aren't looking at the bigger picture.

[cassandravoiton]

If code runs faster then the user time is wasted less as well. That seems in alignment with the ideas behind the video.

[gdg92989]

I don't want to hear the "faster programs save the user time too" argument its total BS. the vast majority of CPU time is spent waiting for the user. So while you're on a holy quest maximizing 100,000 instructions down to 1,000, every second that the user wastes dealing with your neglected UI 1,000,000,000 cycles are wasted (and that's on a machine with a single 1ghz processor).

[NerdsCentral]

The post is talking about servers. Most scripting is for code running on servers. Servers do not wait for the user. Your comment has zero merit.

[gdg92989]

no.. your comment and your whole shortsighted video have no merit. Servers spend time waiting for users as well. Whether its waiting for the next HTTP request or the next batch processing job servers wait for people too.

[NerdsCentral]

OK, I'll explain this as you clearly have no idea what you are talking about. When one commissions a server or server farm it is done against a service non functional requirement. For example 1 second page serve time at peak load. This means that a lot of the time the servers might be waiting but not a peak load. Never the less, modern servers will clock down if waiting. Now, what sets the peak load is the efficiency of the software and the number of people using the server and/or the run length of the batch jobs. The more efficient the software the less servers are required to meet the peak load and so the less power is used all the time. Further, the more efficient the software the less often servers will have to clock up during off peak times. Do you finally get it? If not - I suspect you have zero idea about large scale computing and are here only to defend your lack of ability to program anything other than scripts.