Not exactly, but asking "where to install the server & client and what are the system requirements for each" is not that different to asking "where to install the client and what are the system requirements for it", even when there is no server.
> Have you grown concerned that once the system moves into production the O&M team won't know how to operate "yet another database"?
Yes. Because the production concerns of SQLite are not nil.
> Do you spend agonizing hours trying to figure out if it supports multithreaded connection pools for multi-user writes?
Not agonizing hours, but it is just a slightly rephrased version of a valid question about SQLite w.r.t. concurrent file access (as with locks on file access for any file). Other commenters have brought this up in terms of multi-user access slowing down applications, and setting up intermediary DB access processes using IPC to facilitate this.
> The people asking these questions are stupid
I disagree
> no different than "CSV is serverless" or "JSON is server-less"
CSV and JSON lack any protocol or queryable interface: unless you're using some ancillary tool like `jq` as a comparison, CSV and JSON as filetypes are both "serverless" and "clientless" so not particularly comparable. An article on those would be quite different.