My opinion might be a little biased as I love Wicket... but
1- Except maybe for Web Components I haven't seen anything as reusable as
Wicket (http://webcomponents.org/) on JS world (disclaimer I'm not a big JS
expert, just maybe an advanced user)
2- In some places, companies I have worked for as consultant, I have seen
projects that they considered complex because the JS paraphernalia. They
were be just trivial using Wicket. The sad thing is they did not have any
need to scale. So, something like wicket was more than a perfect fit. They
all used REST and some JS machinery (they also did not plan for mobile so
REST was not needed). Some of these applications were not very DRY... and
REST layer was kind of a mess where you never knew for sure what was
actually used and not.
3- IMHO wicket adoption was hampered by big players support to JSF.
4- One big advantage of JS is how easy it is to find developers and how
large/active communities are.
On Fri, Oct 14, 2016 at 6:33 AM, fzb <naz...@bzforce.com> wrote:
> 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
> 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.
> 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
Regards - Ernesto Reinaldo Barreiro