>From the posts so far this is what i understand.. 1. JS based apps are best suited for high scale applications.. It is worth the effort you take to build and maintain such apps..
2. Wicket can scale only to certain extent based on the server capacity ? If so how to quantify ? (What about load balancing ? What about stateless pages ? Why it does not scale ?) 3. JS based apps resource availability is plenty.. So for new projects better to go with these ? - What if the maintaining these apps becomes tedious due the cons of these JS discussed earlier. May be some more insights will help us all understand, how to choose what depending on the scenarios in hand. - fzb -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-vs-JS-frameworks-tp4675771p4675796.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
