jwrallie
Joined 4 years ago
Joined 4 years ago
It can also depends on the downlink bandwidth available and power/energy budget, so the optimal strategy will differ.
It can be misleading at times though, for example some interesting feature may happen to be just a compression artifact. A cloud looking like some strange human-made object for example, happened to us one time.
Or maybe a more fundamental question, how do you find out what are good packages to use?
Nowadays I’m receiving longer emails than usual and longer code to review. Less spelling errors, but long and pointless prose. Less superficial bugs but more sneaky, fundamental problems.
There is also the trap where you go from 0-80% immediately but end up spending time anyway fixing the last 20%, and it’s unclear if there was a benefit or loss in productivity. Sometimes the almost there rabbit hole of prompting can be misleading.
People need to be open to experiment and make their own judgement based on observation without relying purely on their environment and authority.
The only case where I do find Flatpak useful is to install proprietary electron based applications that do not interact with the rest of the system so much, but I try my best to avoid using those in the first place.
It’s not pretty nor great with bad connections, but there is basically no maintenance.
The other day someone asked me why I use Firefox. I realized the only other browser I use is Safari.
[0] https://github.com/iflow-mcp/rhblind-emacs-mcp-server