4 ms·

I have dropped the server side frameworks in favor of Dojo, jQuery and Backbone. I use JAX-RS as my service layer to provide RESTful services to the newer stack

by kls 15y ago

I have dropped the server side frameworks in favor of Dojo, jQuery and Backbone. I use JAX-RS as my service layer to provide RESTful services to the newer stack. I have seen more and more developers abandoning the server side page frameworks in favor of the JavaScript frameworks and a REST API. JAX-RS with the JPA is a pretty nice set up for developing modern web apps, and I think we will see it's adoption increase for those that elect to use Java for their back end.

chc 15y ago
I'm not the downvoter, but since I hate silent downvotes, this is probably more or less the reason: This kind of app might be fine on the platforms where it's tested, but tends to have severe performance problems for others. Many of us have had our computers bogged down by very resource-intensive web apps, and this "Do everything on the client" philosophy is a common culprit. Exchanging ~50 ms on the server for ~250 ms on the client can become really user-hostile as you get further from the best-case scenario.
- swah 15y ago
  The server still does all the heavy resource intensive stuff, the "business valuable" part. He is just moving templating and managing of state to the client. I have the impression though, that a single page app will reveal problems like increased memory usage where in the classical way of writing webapps would be hidden by the constant page reloads (where hanging objects would get GCed anyway).
- kls 15y ago
  Inefficiencies are due to sub standard development practices or non-optimized technology. The fact is the client side frameworks have matured to the point, where if used correctly they can provide the same performance metrics as server frameworks. In some cases they provide patterns that lend themselves to better usability and can actually make the application feel more responsive. While it is true a badly designed server side page does not bog the client machine down, the fact that it is client side does not guarantee that it will bog down the client. No matter which side of the fence you develop on, if you have a page that is not performing, you have a usability issue and it needs to be addressed. This is less of an issue with the technology and more of an issue with how the technology is being uses or rather misused. I understand that people are dogmatic about this subject and that is why I received the downvotes, but to ignore the fact that it is the way the web is moving is to ignore a massive trend that is well underway.

by kls 15y ago

chc 15y ago

I'm not the downvoter, but since I hate silent downvotes, this is probably more or less the reason: This kind of app might be fine on the platforms where it's tested, but tends to have severe performance problems for others. Many of us have had our computers bogged down by very resource-intensive web apps, and this "Do everything on the client" philosophy is a common culprit. Exchanging ~50 ms on the server for ~250 ms on the client can become really user-hostile as you get further from the best-case scenario.

swah 15y ago
The server still does all the heavy resource intensive stuff, the "business valuable" part. He is just moving templating and managing of state to the client. I have the impression though, that a single page app will reveal problems like increased memory usage where in the classical way of writing webapps would be hidden by the constant page reloads (where hanging objects would get GCed anyway).
kls 15y ago
Inefficiencies are due to sub standard development practices or non-optimized technology. The fact is the client side frameworks have matured to the point, where if used correctly they can provide the same performance metrics as server frameworks. In some cases they provide patterns that lend themselves to better usability and can actually make the application feel more responsive. While it is true a badly designed server side page does not bog the client machine down, the fact that it is client side does not guarantee that it will bog down the client. No matter which side of the fence you develop on, if you have a page that is not performing, you have a usability issue and it needs to be addressed. This is less of an issue with the technology and more of an issue with how the technology is being uses or rather misused. I understand that people are dogmatic about this subject and that is why I received the downvotes, but to ignore the fact that it is the way the web is moving is to ignore a massive trend that is well underway.