Tell me please, who knows what about JSF?

Tell me please, who knows what about JSF? and how promising and popular use JSF
September 19th 19 at 12:28
3 answers
September 19th 19 at 12:30
Currently very promising and popular UI framework, along with GWT and Spring MVC
Unlike JSF of Spring MVC is not too big? it is also used Bina,only JSF is binding directly to components of the form - Reymundo_Hilll72 commented on September 19th 19 at 12:33
: Nothing to do. - reuben.Bartolett commented on September 19th 19 at 12:36
I do not agree, haven't seen that JSF used in large projects. In small saw, and then spat - reuben.Bartolett commented on September 19th 19 at 12:39
never seen any framework for visualization, which is not spitting... Have a JSF (or rather its implementations) has its pluses and minuses, like any other technology. - Lurline_Hanse commented on September 19th 19 at 12:42
: believe in gwt spit less angular on the spit for even less, react about as well) - reuben.Bartolett commented on September 19th 19 at 12:45
: well, I don't have to take your word about GWT, I have experience in JSF and GWT, and perennial. It's completely different technology, it is difficult to compare them. Even the paradigm is exactly the opposite - GWT is a Single Page, JSF also allows you to do more classic and Single Page. On JSF "spit" more because the barrier to entry is much higher. Moreover, this threshold starts to be felt immediately, but later, when it comes to complicated things. Once this threshold is crossed, most of the tasks are implemented quickly and beautifully... - Lurline_Hanse commented on September 19th 19 at 12:48
: I also have experience with GWT and JSF. Don't know why you have decided that it is above the threshold of entry. He spit on the unreasonably high cost of memory and for any reason to poll the server(well, it's the inability to cook, but even so) - reuben.Bartolett commented on September 19th 19 at 12:51
: the memory cost is only one of the mass properties of the framework, and, as I said, every technology its drawbacks and its advantages... JSF - server solution, so he needs the resources of the server; the GWT is JavaScript, which allows a considerable part of the computation to move to the client. Over-consumption of resources: I have now startup using JSF turns on virtual hosting. There Are Windows (!), it MySQL and Tomcat together. The server is allocated 1GB memory, the actual consumption 90% of the time - 600MB. There was a time when I 2 months did not come back, and during that time "flowed" 400 MB; it turned out that their "ate" a couple of Windows services that I just disabled. The application periodically has to handle the load to 20 requests per second for a long time, without any problems with responsiveness. Anyway, nowadays the resources of iron are a dime... - Lurline_Hanse commented on September 19th 19 at 12:54
September 19th 19 at 12:32
Don't bother to JSF. Have not seen any offices at which various projects use the same technology, all are different, need to be savvy around a little, experience will come with projects. And JSF is rarely used.
September 19th 19 at 12:34
JSF - is it for internal network projects, where the data channel is a local area network (why so few public projects on it).
For it has many supplements, sets of ready-made components (1, 2, 3). Quite convenient to build a complex responsive interfaces, it is itself a component, and integrates well with JavaEE applications.

But for Internet sites it is quite ill-suited.

Find more questions by tags Java EEJavaJSF