rounce

Is it? Do you have any examples?

There’s also the other thing of being able to read documentation. If one wants to use some module in one’s project, the datasheet and application notes aren’t going to have breadboard-centric illustrations, they’re going to have schematics (or at least abstracted ones). I presume you come from a programming background, and so would know the importance of being able to read documentation, and knowing that if you can’t do that you’re pretty much dead in the water.

The hard part of learning about electronics is not identifying the components but getting a good understanding of what is happening in the circuit. For that, it’s better to have a learning tool which displays voltage and current at every part of the circuit all the time. Rather than something which prioritises looking like what you’d have on your desk as a constraint for its method of visual representation.

0: https://www.falstad.com/circuit/circuitjs.html

The workaround mentioned isn't a magic solution, it fails in a bunch of more complex cases too. Chamfers are a complicated operation and predicting valid values across of the operation in order to set a maximum value is, as far as I'm aware, in a similar region of difficulty. It would also be unfeasible in many cases to attempt the actual operation across a wide range of values. It's not so much a choice as just being hard to do.

Which is something I find odd that so many people seem to assume GIMP as the de-facto open source photoshop alternative when Krita is more analogous and much easier to use.

I'm guessing you're trying to set a fillet which would completely consume one of the faces adjacent to the edge being filleted. In these cases I've found that a workaround is to make the fillet 0.001mm smaller than the size which would consume the entire face. You end up with a very very small amount of flat area but it's so small it doesn't show up during machining or 3d printing.

I also am not a fan of the icon-only toolbars and so I always use this plugin: https://github.com/APEbbers/FreeCAD-Ribbon

IMO it's a big improvement (I have it configured to only show small sized icons with labels) but then again I know not everyone is a fan of this type of toolbar because of the amount of screen space it takes up.

I’d argue you still can’t do it, you just have access to cheap enough labour that you can afford to have it done for you on a scale which you couldn’t before. However seeing as you haven’t developed those skills in the first place you also lack the ability to make any deep critique of the output you are given. Instead of guiding it in the way someone experienced would, you’re still the client, except now you’re the client of a machine.

  {
    nix.gc = {
      automatic = true;
      dates = "weekly";          
      options = "--delete-older-than 30d";
    };
  }

Alternatively, given you’re running NixOS you can just override the `src` of the derivation with a newer version. This is part of the point of running NixOS: making small modifications to packages in the fly.

This is already the case in the UK, and the EU too as far as I’m aware.

Edit: just looked up LazyVim and it seems to just be a prebuilt neovim config atop the VSCode-Neovim extension which was one of the aforementioned janky experiences (IIRC undo stack wasn’t shared with VSCode and would get out of sync). I think I tried it as a last ditch effort because someone else said that it’ll fix VSCode-Neovim plugin deficiencies but I ended up just going back to my simple but effective neovim config and using VSCode as a visual debugger. I’ll give it another go if you reckon it’s much better though.