Hello all,
Is the topic "Wicket in Action" the book meant, this was a
misunderstanding, sorry!
I myself still work with Apache Wicket 8.x and maintain a product with
it. We have written our own components and removed the third party
libraries because they are no longer maintained.
In the past years the number of developers, extensions and examples on
the internet has decreased a lot.
The framework is good(!) and it allows a very good base for server-side
rendering without all the JS technologies.
It was noted that many things depend on the scope, requirements, and
knowledge of the developers. Yes, this is all correct!
However, Apache Wicket is comparatively as complex as the modern JS
frameworks and I don't see the Java vs Javascript argument as serious
here. It's more about innovation, product maintenance, and security in
the choice of framework. This includes release cycles, bug fixing,
documentation, and the number of users of a framework. These factors
demonstrably decreased and for a new development or continuation of a
project a risk!
Kind regards
Kyrindor
Am 13.05.2023 um 16:41 schrieb Andrea Del Bene:
Hi,
I think you have misread the title of the original mail which is about
a book, "Wicket in Action", and not about Wicket itself. That said, I
agree when you say that for Wicket might be difficult to find plugin
and integration libraries available out of the box. That's because
Wicket is completely lead on a voluntary base and it's not backed by
any company. But I completely disagree with your conclusion. Wicket
remains highly flexible and can be used to implement application of
any size without embrace the canonical JS development stack (npm,
node, css compilers, etc...) which I personally find overcomplex and
overbloated to use. In this regard a powerful tool to use with Wicket
(and with many other Java web frameworks) is project WebJar, which
makes css/js libraries integration quite easy: https://www.webjars.org.
Andrea.
On 12/05/23 20:14, Kyrindorx 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
Disadvantages:
- modern plugins for Wicket: outdated and quite little.
- CSS Libs like Bootstrap: outdated and strong coupling (plugin)
- use of modern JS techniques + Wicket: difficult
Conclusion:
For medium sized sites working with Apache Wicket basic components
and using Java, HTML and Wicket JQuery > ok.
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!
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.
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, <ja...@mcruncher.com>
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: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
