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

help-circle

  • Stick with Windows. Microft will deliver paradigm shifts and you will have no say in the matter. They are already removing options for disabling Copilot, and for all the promised backward compatibility they are letting go of features that lots of old Windows software depended on, as they introduce features similar to ones in Linux. I cannot really fault them for all of these changes, but the difference is actually one of choice and privacy, and not really the one you seem to think it is.



  • If you convert the chemical energy in a unit of coal to heat (burn it) you can calculate how much energy exists in that coal, measured in appropriate units (e.g. kWh). That is evidently what this author is trying to dumb down as “invested energy”. The amount of energy extracted as electricity is typically 40% of that… the rest ends up as heat which is much less useful than electricity.

    I agree that this is not particularly useful in discussing the merits of different energy sources because good design tends to do as well as is practical and the supply of fuel and negative impacts of that process can’t vary dramatically.






  • 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.