Hi, On Fri, May 12, 2023 at 9:14 PM Kyrindorx <[email protected]> wrote:
> Hey all > > It is compact, has many functions and does its job well. If you compare > it with JSF, Vaadin it compares well. > > Advantages: > - flexible > - Java + HTML > is ok > Huge advantages, only my opinion, you forgot to mention 1. You can do very complex applications with backend developers (Java developers) who know little about JavaScript. You have a team member that knows JavaScript and low level things well and the rest just use components and Java. Many times those backend developers can fix and implement complex issues without waiting for the javaScript guy coming back from holidays. The slogan on NodeJS was JavaScript at all levels. Wicket is Java at all levels (if you have a guru on board hiding JavaScript for the rest of the team). 2. You can maintain huge applications with very few developers. 3. Many applications do not need to scale. Just provide as much functionality as possible with as less maintenance cost as possible. Wicket excels on that. 4. Secure. > Disadvantages: > - modern plugins for Wicket: outdated and quite little. > True. Sadly many companies just want to leach open source and not pay developers to contribute. And developers just want to do trendy things that help you land good jobs. - CSS Libs like Bootstrap: outdated and strong coupling (plugin) > Who forces you to use those libraries? I have used wicket and bootstrap together with minimal use of those libraries. > - use of modern JS techniques + Wicket: difficult > Stated like this, this is just an opinion. One big disadvantage of wicket (IMHO) is it is difficult to grasp and understand for developers. Concepts like detaching and the request cycle are difficult to explain and more difficult to keep pages small after detach. > Conclusion: > > For medium sized sites working with Apache Wicket basic components and > using Java, HTML and Wicket JQuery > ok. > Again this is just your opinion. I have built/worked on many wicket applications with very strong use of JavaScript and very dynamic client side behavior. > > The development of modern JS applications Apache Wicket is (my opinion) > outdated. It very good flexible JS frameworks, more plugins, lots of > docs and examples. And the number of developers for modern JS frameworks > is huge! > True. > > In the end, I think Apache Wicket is past its prime and we are talking > about product maintenance here. I wouldn't develop new big projects with > Apache Wicket anymore. Here it is not the evaluation of the framework, > but the number of projects and the amount of developers that matters. > This depends on your goals and the needs these applications have. > Greets > Kyrindor > -- > > Am 11.05.2023 um 14:23 schrieb Andrea Del Bene: > > If you are new to Apache Wicket it might be better starting with the user > > guide which is meant for a full introduction from scratch and is updated. > > > > On Thu, 11 May 2023, 10:29 James Selvakumar, <[email protected]> > wrote: > > > >> Hi all, > >> > >> Just wondering whether Wicket in Action is still relevant with all the > >> recent changes to Wicket? Can it be used to help a new developer > understand > >> Wicket? > >> > >> -- > >> Thanks & regards > >> James > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards - Ernesto Reinaldo Barreiro
