The note about "concentrating on energy efficiency is misguided" (your words) in the introduction is about server-side energy efficiency. Of course you do have to make your client side (web app, native app) energy efficient:
As part of performance testing, have a look at electricity use, as it will both be directly associated with emissions to produce that electricity, and be perceptible by the user (battery drain).
[…]
Optimize for the perceived performance and battery life.
Could it be the word “first” in the “Pick servers in carbon-neutral or low-carbon datacenters first, then optimize your architecture and code” pullout that made you think I was kind of dismissing the rest? Maybe I should rephrase that… My point rather was: if you care, start by doing that; there's no point investing time in all the rest when you have that relatively easily attainable low-hanging fruit, so that should probably be your first action.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for your comment.
The note about "concentrating on energy efficiency is misguided" (your words) in the introduction is about server-side energy efficiency. Of course you do have to make your client side (web app, native app) energy efficient:
Could it be the word “first” in the “Pick servers in carbon-neutral or low-carbon datacenters first, then optimize your architecture and code” pullout that made you think I was kind of dismissing the rest? Maybe I should rephrase that… My point rather was: if you care, start by doing that; there's no point investing time in all the rest when you have that relatively easily attainable low-hanging fruit, so that should probably be your first action.