> I consider developer productivity and code maintainability to be features. Sure, there are performance tradeoffs, but there are some obvious benefits.
In a client side application,if the app is slow,the users wont be happy about it.
If it takes for ever to load,the users wont be happy about it.
On the server there is always caching so that requests never hit the app itself.
On the client,if the js code is slow ,for whatever reason,you cant hide it to the user.
What you say might be true on the server,these "features" definetly have to be balanced with performances on the client.That's why sometimes it make sense to use React over AngularJS,for instance,because Angular is known to be slow.
In a client side application,if the app is slow,the users wont be happy about it.
If it takes for ever to load,the users wont be happy about it.
On the server there is always caching so that requests never hit the app itself.
On the client,if the js code is slow ,for whatever reason,you cant hide it to the user.
What you say might be true on the server,these "features" definetly have to be balanced with performances on the client.That's why sometimes it make sense to use React over AngularJS,for instance,because Angular is known to be slow.