Play is beautiful, Roo is confusing and seems like another me too. Struts, JSF are operating from coffins.
what will survive in 2012 and next few years?
1–10 of 12 posts
Play is beautiful, Roo is confusing and seems like another me too. Struts, JSF are operating from coffins.
what will survive in 2012 and next few years?
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 f…
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.
I personally like how Play has evolved, but adoption is severely thin. They just got typesafe backing but Spring with the muscle behind it might be able to shove the rest away.
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 f…
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…
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).
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 f…
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…
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.
My Favorite is thye Wicket framework. After having used JSF , which is a hellhole, I found wicket to be remarkably versatile and powerful. It integrates cleanly with Jquery. DOJO aw well as Spring. It is the only J2EE framework where designers can tweak HTML templates without the programmers having to worry about integrating those changes back.
My default reaction to HN hipster kiddos eschewing Java for web development based on hearsay/generational bias/fashion is to roll my eyes and simply not post, but in this case I'm glad to see there's at least someone else on this site that experiences the virtues of Wicket.