Any reasonable person would have assumed that if you wanted to talk about backgrounding, you wouldn't have used a word with a very different meaning to refer to it. As I said, the fact that it was possible to infer the intended meaning does not mean it's obvious; the interring process being required proves the opposite.
> And if I don’t get to decide if things are “obvious” then you don’t get to decide if you’re being reasonable.
Of course. I might be not. But what I'm sure of is that I'm honest and I'm giving you a piece of information that may make you better at communicating in the future, entirely avoiding discussions like this one. Whether you use it to improve yourself or decide that I'm "unreasonable" is up to you and your ego.
> I do not think it should be the default behavior for something that will spend most of its life in someone’s pocket (by design)
If I don't want an app to run, I close it. If I do want it to run in the background, I don't close it but put it in the background instead. If I don't want to use the phone at all, I suspend the whole device. This is the design that has worked perfectly well on my phones for almost two decades now and was always the default there.
This is getting circular. I think you're actively lying if you say you didn't immediately parse what I said. I think you knew what I meant immediately, and I think you're being needlessly pedantic, which is fine but I think you should just be upfront about that.
I used a word arguably incorrectly ("closed") (though I would like to point out the iOS shortcuts uses that terminology as well), but the surrounding context about being backgrounded makes it very apparent.
Keep in mind, the person who initially responded started giving me a lecture about single-tasking operating systems, as if I don't know that most operating systems are multitasking. Pretty much anyone who frequents this forum will know that operating systems are multitasking, and given that and the fact that I said "backgrounded", it should be immediately obvious what I meant. Neither I nor anyone else here needed to explain to me (or most other people) about multitasking operating systems. This is what I was initially responding to, because the person told me to "Please learn what's what in the system you're using", which is pretty douchey in general, and especially douchey since they're lying about not understanding what I meant.
If I didn't have to ask myself the question "wait, so did they actually mean 'closed' or was that supposed to mean 'backgrounded'?" before I could parse the comment I wouldn't have bothered replying at all.
> And if I don’t get to decide if things are “obvious” then you don’t get to decide if you’re being reasonable.
Of course. I might be not. But what I'm sure of is that I'm honest and I'm giving you a piece of information that may make you better at communicating in the future, entirely avoiding discussions like this one. Whether you use it to improve yourself or decide that I'm "unreasonable" is up to you and your ego.
> I do not think it should be the default behavior for something that will spend most of its life in someone’s pocket (by design)
If I don't want an app to run, I close it. If I do want it to run in the background, I don't close it but put it in the background instead. If I don't want to use the phone at all, I suspend the whole device. This is the design that has worked perfectly well on my phones for almost two decades now and was always the default there.