• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle


  • As you add more compute per user interaction (“smart” features), you increase power consumption. To keep an 18hour discharge cycle, you have to have more battery. Since phone thickness is a negative marketing feature but increased screen size is a positive marketing feature, you end up with bigger phones.

    Every time they reduce compute power consumption, feature inflation overtakes the gain and more power is needed over time. Try turning on battery saver in the morning… even with “normal” use the battery will last significantly longer due to disabling background power consumption.



  • Bash is always there, and bash scripts and snippets are precise. Describing gui manipulations when the GUI keeps changing is also quite hard… what if the person you are interacting with has a 2-yo system and you have the bleeding edge? Even knowing which menu the settings are in can be frustrating for the helper.

    Windows users (e.g. me at work) get grumpy when Microsoft starts changing the menu structure after keeping it consistent for 20 years and start thinking of powershell scripts to create consistency between our engineering workstations.




  • They are text files. If there is anything weird about them it is that they are indented with spaces and if you are inconsistent with indentation they won’t read into the yaml import function, but I can’t imagine why vim or nano would have a problem with opening them. Maybe the ones you were using were not actually yaml.