I don't think that the examples that you have with the waitress and the mechanic are good comparisons, because they are "cute" after solving your problem. More accurate examples would be the waitress or mechanic saying "Oops, sowwy! Something went wrong." and leaving, without solving your problem.
I'm also on the side of being professional while the problem still stands, because the user is most probably annoyed at the situation, and wants you to take it seriously. You can be cute after the issue has been resolved.
Yes, that and the openapi plugin is what i use right now. Before i used to load the ts compiler at runtime and tell it to parse my file and got the types from there. But it was a stupid overengineered brittle solution.
The other article you mention comes from the same website: https://rxdb.info/offline-first.html. It's in an opinion section, giving the arguments from both sides.
Yes. I have written both of them, mostly to make sure I trigger 100% of people, no matter if they like offline first or not.
I mean, read all these comments on both articles. People say offline first does not work, then they say that every software is offline first by default and it is nothing new.
It was totally worth it spending two 3 days on it :)
I feel like you missed the most important point of "offline first" is that your data belongs to you and does not need to be shared to the cloud in order to have tremendous value. The code/logic to enhance your data should be shipped to you, rather than the other way around.
Yes, I totally missed this side of the dice. Having your data stored locally, being in control, being able to reset the state to it's origin, export the local state as json and import it somewhere else, knowing what is stored and how long.
