Just a basic programmer living in California

  • 4 Posts
  • 43 Comments
Joined 4 months ago
cake
Cake day: February 23rd, 2024

help-circle


  • From what I’ve learned revolutions are often accompanied by circumstances where people are desperate due to lack of basic necessities, especially food.

    The French revolution was preceded by a serious food shortage. Remember that “let them eat cake” comment? One of the key events, the Women’s March which displaced the king and queen from Versailles, was specifically motivated by demands for food.

    The European People’s Spring saw lots of revolutions across Europe in 1848-1849 including in France, Italy, Bavaria, Austria, Hungary. That was about the same time as a continent-wide grain shortage on top of an economic crisis.

    The Russian revolution of 1917 came at a time when a combination of WW1, bad leadership, and an extra cold winter led to food shortages, and fuel shortages so people were starving and freezing at the same time.


  • It could be good, but there is a conflict with one of the electric car hurdles: range anxiety. I use a level 1 charger at home which works fine for regular use - but it does take about 4 days to charge a nearly-depleted battery up to 80%. I’d be loath to give up energy that takes such a long time to get back. But this system would presumably require a level 2 charger, and that might make it ok. Still I can imagine objections over not having a car charged when you want to make a longer, last-minute trip, and over battery depreciation due to more cycling.













  • It’s great that the system is so efficient. But things do come up. I once worked with an LSP server that was so hungry that I had to upgrade from 32 to 64gb to stop the OOM crashes. (Tbf I only ran out of memory when running the LSP server and compiler at the same time - but hey, I have work to do!) But now since I’m working in a different area I’m just way over-RAMed.





  • It’s possible (and I think advisable) to set your flake nixos config to set the system flake registry to point to the same nixpkgs revision that your flake uses. The nixos-starter-configs standard template has two lines that do this:

    # Opinionated: make flake registry and nix path match flake inputs
    registry = lib.mapAttrs (_: flake: {inherit flake;}) flakeInputs;
    nixPath = lib.mapAttrsToList (n: _: "${n}=flake:${n}") flakeInputs;
    

    That actually adds all of your flake inputs to the system flake registry. So for example if in addition to your nixpkgs input you also have an input you named nixpkgs-unstable then can also reference that with stuff like nix shell. For example:

    nix shell nixpkgs#hello nixpkgs-unstable#cowsay