It depends on what your metrics are for energy and resources. Are you talking about the end user hardware, or are you talking about developer time and effort. If it’s the former, you’re right, if it’s the latter you’re completely wrong. And while there’s merit to your point (if it is about end user storage, energy consumption, etc), that’s not really in short supply while open source developers free time is.
Where I live, most electricity is hydroelectric, nuclear, or wind. So it’s really NBD to download a few extra MBs of data, especially since flatpaks aren’t something you need to download over and over again.
I can see how it’s an easy fix but IMO it’s a waste of energy and resources to pack up all dependencies for every app.
Flatpak is inefficient, but very convenient. The impact of “package once, use anywhere” is huge.
It depends on what your metrics are for energy and resources. Are you talking about the end user hardware, or are you talking about developer time and effort. If it’s the former, you’re right, if it’s the latter you’re completely wrong. And while there’s merit to your point (if it is about end user storage, energy consumption, etc), that’s not really in short supply while open source developers free time is.
developer time and effort has to increase 100 fold to even touch the energy waste larger downloads create.
How much more efficient do you recon the developers are because of flatpack? Does it quantify against the bandwidth and storage needs?
Where I live, most electricity is hydroelectric, nuclear, or wind. So it’s really NBD to download a few extra MBs of data, especially since flatpaks aren’t something you need to download over and over again.
Nice - so no impact as you have hydro. Got it
Not “no” impact (the laws of thermodynamics are still a thing), but it’s pretty negligible.