On Sat, Oct 15, 2016 at 3:44 AM, fzb <naz...@bzforce.com> wrote: > Thanks Martin for the reply. Understood the points conveyed. > > > Martin Grigorov-4 wrote > > It scales with the knowledge of the engineers. > > It is not just Wicket when you need big scale application. > > It goes from the OS configuration, to the selection of the databases, the > > web server config and good application code. > > Is there any place or topic, where we consolidate all best practices & > learnings ? >
There are some best practices in the user guide. I have some more in my training materials. But anything that is applicable for other web frameworks is applicable for Wicket too. If you have specific questions how to do something then ask here. > > > Martin Grigorov-4 wrote > > I personally try to use only technologies that *I* like, not because the > > marketing team of some company said that their product is the best. > > Yes, agreed. But not just marketing team of that company, the industry > trend > is more towards those JS frameworks like Angular, React etc.. So wanted to > Since you mentioned Angular. Angular 1 is not very scalable. Any performance test will show you that after some size the logic it uses for diirty checking becomes its bottleneck. So for me Angular became popular because of its easier testability, not because of its performance. Angular 2 has almost notihng in common with Angular 1. This should tell you a lot! There are much more performant JS frameworks than Angular and React but since they were not created by big players (like Google and Facebook) they didn't got the same attention from the industry. I.e. your manager will more easily approve you to switch from Wicket to Angular 1 (despite its known problems) because it comes from Google than to switch to Ractive.js that is developed by just few people, no matter it is has much better performance than Angular. > know where do Wicket stand against those.. We wil be in a better position > to answer questions down the line.. As an Architect when you make > decisions, > I see no concrete questions so far in this thread. Asking someone to compare you X vs Y vs Z in general is way too broad. > you need to stand by those and prove it.. This topic was intended to > clarify & get more insights to be able to make decision. > > - fzb > > > > > > > > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/Wicket-vs-JS-frameworks-tp4675771p4675798.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 > >
