> Also there is nothing classic about "server-side" MVC : it is ridiculous and never made any sense.
Given that the server doesn't produce any HTML, I agree with you more or less. On the other hand I like a separation of apps/modules into data aquisition (pulling the data into memory, producing something digestable) and the actual (business) logic. Mixing both up can bring you into hell's kitchen if the complexity is high enough.
After all MVC is anyway only a very loose recommendation. In practice it is not possible to distinct between M, V and C 100%. Anyway, I haven't seen any other global pattern being comparatively successful.
Given that the server doesn't produce any HTML, I agree with you more or less. On the other hand I like a separation of apps/modules into data aquisition (pulling the data into memory, producing something digestable) and the actual (business) logic. Mixing both up can bring you into hell's kitchen if the complexity is high enough.
After all MVC is anyway only a very loose recommendation. In practice it is not possible to distinct between M, V and C 100%. Anyway, I haven't seen any other global pattern being comparatively successful.