I’m sorry I don’t getting your point . You start off by agreeing that you don’t like the extra complexity that the update statements give. Then do some pseudo code of something entirely different where we all already agree is not an issue.

Then at the end your conclusion is that it is totally feasible. Why? You still didn’t adress the problem of updating the state

Ok, I mentioned a state machine in another sub thread. It’s not as bad if you already have a state machine.

It’s still adding more complexity though - again when the value is updated. You still need to change the state when saving. You need to decide which state to use when starting the game.

There is still risk of screwing that up when refactoring. And still the value is nearly none.

Regarding state mchines, it’s a complexity in itaelf to add random flags ro the state machine. Next time you want to add another flag you need to double all the states again, e.g. PAUSED, PAUSED_AND_SAVED, PAUSED_AND_MUTED, PAUSED_AND_SAVED_AND_MUTED. I would never add mute to the logic of the menu but that’s the pnly example I could come up with. Maybe you see my point there, at least?

Plus all the lines to update the state, when the menu is closed, when the game is closed (i.e should it be true or false at startup), when the game is saved obviously.

That’s at least three more lines plus the one you mentioned for no extra value. And again it’s easier to screw it up e.g. while refactoring.

The state “the game is paused” is different from " the game is paused and saved". Sure that could be another key in some atate machine but like above: it’s the “not mess it up” part that is harder.

It’s the “don’t mess it up” part that is harder.

They solved that by having most of the game revert to starting positions frequently (e.g. every time you die, area load).

Maybe not as immersive as Bethesda games but their lore at least tries to make sense of it.

It’s more like playing the Edge of Tomorrow movie, you need to learn where everything is.

That’s harder to implement. Suddenly you need to store that extra state somewhere and don’t mess it up. The last save should already have a timestamp and is immutable. A lot less likely to get bugs that way.

And fuck your versioning system. And you dependency management. And tooling. Why are there like five different projects trying to lock down the python environment? Conda? Venv?

Even Ubuntu tries to lock down python so that it doesn’t brick the install due to dependency conflicts.

Thanks. I wish the link could be created from the f-droid automatically. I’m too lazy to try to paste the parts together

The pro version of OsmAnd is free on fdroid!

Same in EU

I use Vespucci, it’s advanced but still pretty easy if you just want to do basic editing. https://vespucci.io/

P.s. how do you link to an app on fdroid?

But you can also just flag it if editing is not your cup of tea. Here’s a convenient, non-techy tool to add notes for others to use when editing: https://www.onosm.org/

It’s even worse when you can tell they really tried and still end up with spaghetti. Even mid- to senior developers do this. Rhe more senior they claim to be are, the more embarrasing when you have to get the stick.

Some people try to be so clever with fancy design patterns or bit-tricks, instead of just solving the problem, you now have two problems and a solution to one of them.

It’s actually the company’s problem. They usually opt to add more debt though, rather that wade through the old stuff.

In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It’s usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and “future proof”. The only future proofing that happens is that no-one will understand it, so they won’t change it. Trying to design for the future usually makes it harder in the future.

That’s the usual open source way. The config probably came later so they just added the option without changing the default because that would break backward compatibility.

And there would be too much boring work to build a migration.

Bank holidays would be really awkward. You start wort at 23 and the next day is off so you would just have to work that one hour.

Office workers could probably move hours around. It would get complicated for shift workers though. Paying overtime for work on holidays?

Exactly! All applications can be shit, not just web sites.

People screw up CLI’s all the time (looking at you Google Cloud). They (used to) insist on using my installed python which automatically upgrades and breaks the CLI. Good job python. Good job Gcloud.

Yes you should. I think most comments here are about products that have millions of users where it’s actually worthwhile spending all that extra time and money to perfect things.

For most development, it isn’t worthwhile and the best approach is to wing it, then return later to iterate, if need be.

The same goes for most craftsmanship, carpentry in particular. A great carpenter knows that no-one will see the details inside the walls or what’s up on the attic. Only spend the extra time where it actually matters.

It triggers me immensely when people say “I could have made a better job than that” about construction work. Sure maybe with twice the budget and thrice the time.