this is a topic every web developer is facing currently.

I think because Wicket uses HTML5 and Java you can combine JS Frameworks with 
many of the features of Wicket. Example: Because you have a java backend you 
can build a rest API with wicket-rest-annotations and configure your Angular JS 
to work with it - if you have a page change you could use Wicket components and 
even the pages could be served with Wicket containing the Angular content.

There are some things I want to point out:

Java Frameworks:
* Compiling / JUnit tests (with WicketTester) let you know if you break 
something - in my opinion this is currently working better as 
JavaScript-Testing with no compilation
* You have a better IDE support for the Java Part than for JavaScript - all the 
time I spoke to JS developer they all the time give me a complete different 
tool setup they use which at least do not cover the whole stuff needed to 
ensure alle facets if you refactor something (this gets better with TypeScript 
which also Angular decided to use)
* NPM itself does not guarantee that the versions you are using of a released 
module are the same all the time - you have to use additional plugins like 
Shrinkwrap to do so - this is way better in maven!
* You don't have to build up the interaction client<>server yourself (Wicket 
and others) this is done by the framework for you - with Angular you have to 
handle every REST call yourself

JavaScript Frameworks:
* You don't need a VM to run it just a simple browser and the library
* A big community of developers, because every frontend developer used 
JavaScript before can build up the presentations layer.
* Less overhead on server side (memory consumption)

As you can see there are advantages and disadvantages on both sides, but as I 
mentioned - if you want to you can combine them, but you have to evaluate which 
fits the best to your requirement.

kind regards


> Am 14.10.2016 um 06:33 schrieb fzb <naz...@bzforce.com>:
> Hi,
> I am a fan of Wicket & had been working on for last 6 to 7 yrs using the
> same. Recently had evaluated few frameworks Angular, ReactJS etc in view of
> developing new applications, I did not feel them appealing may be due to my
> very bad java script knowledge.. if at all i learn and start working on it,
> I felt I am not going to be productive on it. Currently I feel Wicket due to
> its Component based is very much productive and helps to give the
> consistency across application in terms of look n feel etc. 
> Just thought of hearing comments from others as well ..  Are those using
> Wicket, using other frameworks as well.  Are there any combinations which
> works well with Wicket or otherwise. 
> - fzb
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Wicket-vs-JS-frameworks-tp4675771.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

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to