this post was submitted on 28 Jun 2023
30 points (100.0% liked)
Programming
13386 readers
1 users here now
All things programming and coding related. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Very interesting! Thank you for sharing your project!!
However, in terms of some of the benefits you mention in the "motivations", bandwidth, energy efficiency and CO2 might weak points: after all your server (backend) stays on 24/7 and it does all the heavy lifting anyway, doesn't it? So you are not really saving bandwidth/energy/CO2... (unless - of course - you cache in "time" and "space" and reuse the search results for queries of yours and of other users).
Yes, I didn't research this extensively... it was more of a hunch. :D Yes, certainly, I simply thought that if you minimize phone usage, it would result in a longer battery life and fewer charging cycles, which in turn would reduce CO2 emissions... but I admit it's a bit of a stretch. :D
It's pretty complicated. Something like half the emissions / footprint of a phone or computer is in the manufacture of it so anything that means people don't need to replace their device is a win, regardless of battery life or power usage.
A lot of servers are run off renewable energy. If you check out the sustainability pages of AWS or Azure they both talk a pretty good game. Plus if you're using some flavor of serverless there isn't really a dedicated CPU core just for your app so sometimes the server side of it would be using zero energy as it's gone to sleep.
We really need to get to grips with how to measure the 'ecological weight' of software in a simple, reliable and transparent way.