Only in programs with 100% cpu use? If Python or JS sit idle waiting for user input, are the efficiencies really so different? Developer time also has energy

Only in programs with 100% cpu use? If Python or JS sit idle waiting for user input, are the efficiencies really so different? Developer time also has energy cost in AC, transport, etc for a human. What about the fact that the cost of web inefficiency is offloaded to the user? Users pay the power bill for the overcomplicated, slow, unnecessarily CPU intensive front end. So, at a surface level, what you say is true, but the deeper picture is complicated. The tooling, too, has gone a certain way... making a native GUI is now slower, less documented, less catered-to than web UI; in my opinion, for most simple to moderately complex UIs, native is going to take twice as long to make look good... but that inverts, in my experience, as the program and UI become more complicated. It's also strange that the UI itself is so bloated and developmentally time consuming. We lived on the CLI once -- maybe in some not too distant future a killer app can once again show consumers the power of the command line. After all, google/Siri/Alexa do just that.