I feel like I'm repeating myself, but serverless means you don't care about servers when running your code At all. That's it. Your examples above don't fit into that at all, so they aren't really applicable.
You submit your job, function, whatever and it...just runs. You don't have to worry about servers, hence the name. Not sure why everyone feels like arguing over a simple concept, but alas.
> but serverless means you don't care about servers when running your code At all
We already have semantically useful terms/naming conventions for that. Shared Host, Cloud hosted, $LAYER-as-a-Service, etc.. No need to use a blatantly misleading term instead.
You submit your job, function, whatever and it...just runs. You don't have to worry about servers, hence the name. Not sure why everyone feels like arguing over a simple concept, but alas.