By setting a default you're telling the system to use the values defined in the default setting unless the user overrides those values. Default values should remain as originally defined unless a new default is set. This is a standard in software and not particular to BeerSmith.
Ah, it's a "feature" rather than a bug.

I would agree with you if I was talking about a parameter (e.g. grain absorption), but I'm not. I'm talking about a
profile. Saving off a copy of this profile with the same name, and having it exist only in the preferences is
not standard in software.
Doing it this way has two awful traps when editing your default equipment profile:
1. You edit it from the Equipment Profiles area. Then you run into the trap I found, so you need to remember to then go to settings and remove and re-add the profile.
OR
2. You edit it straight from Beersmith->Preferences, which then doesn't update the original equipment profile. Meaning if you then change your default equipment profile to one of your other profiles, you've just lost your new settings to the aether. Or if you make a recipe and change the profile to something else, then change it back to the one with
the same name as your default profile, it will have different parameters!The user should not have to edit their parameters twice to get it to save correctly.
Software should not create another copy of a parameter file with the
same name, but have it exist in a different state.
If config files did this in other applications, operating systems, etc. then things would break super quickly.
Recipe files are independent and stand alone. If you make a change to any profile after a recipe is created and want that new profile to be used you must go back to the recipe and make the change.
That's fine, but also not at all what I'm talking about.
I'm saying when you've specified your choice of default profile, and edit that profile, it doesn't persist in
new recipes.