Maybe you're right that people find it easier to think that way, but it seems rather illogical to me. The very first step in creating this separation is to def

Maybe you're right that people find it easier to think that way, but it seems rather illogical to me. The very first step in creating this separation is to define an API that is implemented and operated by backend devs and used by frontend devs. Once you have done that, you have achieved all the clarity that is necessary or possible. Whether or not some parts of the frontend are executed on the server-side shouldn't matter for the question of who has responsibility for what. Perhaps it's more about the ease of hiring for different skillsets. If frontend is synonymous with client-side and backend is synonymous with server-side, it makes life easier for HR and recruiters.