I guess she is not entirely off, either. It's called that because it is the second division of an hour.

Use any flavor you like, there aren't any rules

Around here we just have little stickers on the produce with a code number on it. Most produce is just stacked with no packaging. You collect as many as you want in a bag. At the check out, the little code number can be used tell what the exact variety is.

This seems a lot simpler than lazer etching to me, but idk, maybe that is really cheap and easy too?

I feel like that requirement comes from mortgage lenders, not the government.

Thing is that it has been shown that the cost doesn't add up. Guild Wars and Guild Wars 2 are both games you only pay the cost of the box, no on going subscriptions and they are able to continue running the servers and infrastructure just fine. 15$/mo just doesn't make sense.

I went through this a couple years ago. Decided Jeff Bezos does not need any more money, cancelled prime. Funny this was that most things ship the same as always, get them in like 2 or 3 days.

In fact, most other online retailers offer similar free 2 day shipping to stay competitive and I usually find stuff of Amazon first.

Any recursive algorithm can be made iterative and vise versa. It really depends on the algorithm if the function calls are a major factor in performance.

The main problem with std:: expected is lack of language support. In theory, it works well as an alternative to exceptions, with nice self contained monadic statements. In practice, it is actually much worse than what the article suggests.

main issues -

1. as I said, no language level support. You eventually end up with messy code somewhere because the library code can't simplify things enough. You end up with if checks strew about that really oaught to be a language paradigm.

2. there is not a lot of code making use of it, so at the boundaries of your code you have to make adaptations to and from std:: expected from whatever some library chose to use.

3. adapting your existing codebase is basically impossible. Perhaps if you are starting a new project you can do it, but it is different enough that all your existing code must be updated to accommodate the new paradigm and it's just an awful experience doing the work and being in a mix of error handling.

In the US, they are quite popular.

These examples didn't actually clear anything up for me 🙃

Does Synology Photos support shared albums where any user can contribute photos?

But with what computer?!