You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Maxim Solodovnik <so...@gmail.com> on 2017/12/21 15:49:30 UTC
Article in Russian about Wicket
Hello All,
Recently I found an article about Wicket in Russian:
https://habrahabr.ru/company/jugru/blog/345036/
I'm afraid the article is negative :(
The main points are:
1) there is lack of developer activity
2) Wicket based applications consumes lots of memory
3) The performance is bad
4) there is no scalability (no cluster support)
surprisingly #3 is illustrated by the speed of wicket.apache.org
IMO this article lacks numbers and "evidences"
I can try to
1) write an article with some numbers to refute this
2) visit https://2018.jbreak.ru/en/
....
WDYT?
--
WBR
Maxim aka solomax
Re: Article in Russian about Wicket
Posted by Maxim Solodovnik <so...@gmail.com>.
Actually article authors welcoming wicket fans to visit jbreak and argue
with them
I guess it also might be sort of advertising ....
You can use google translate to get the idea ...
On Thu, Dec 21, 2017 at 11:20 PM, Andrea Del Bene <an...@gmail.com>
wrote:
> On Thu, Dec 21, 2017 at 4:49 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
> > Hello All,
> >
> > Recently I found an article about Wicket in Russian:
> > https://habrahabr.ru/company/jugru/blog/345036/
> >
> > I'm afraid the article is negative :(
> >
> > The main points are:
> > 1) there is lack of developer activity
> > 2) Wicket based applications consumes lots of memory
> > 3) The performance is bad
> > 4) there is no scalability (no cluster support)
> >
>
> Like many other Java web frameworks scalability can be implemented
> using distributed
> data store (like Ignite or Hazelcast) for web session.
>
> I can't read Russian so I don't know which frameworks have been compared to
> Wicket but I also agree that these conclusions are (to say the least)
> unfounded.
>
>
> >
> > surprisingly #3 is illustrated by the speed of wicket.apache.org
> >
> > IMO this article lacks numbers and "evidences"
> >
> > I can try to
> > 1) write an article with some numbers to refute this
> >
>
> I now it takes a lot of time writing technical articles but it would be
> great!
>
>
> > 2) visit https://2018.jbreak.ru/en/
> >
>
> ...to face the author of the article :-)???
>
>
> > ....
> >
> > WDYT?
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
--
WBR
Maxim aka solomax
Re: Article in Russian about Wicket
Posted by Andrea Del Bene <an...@gmail.com>.
On Thu, Dec 21, 2017 at 4:49 PM, Maxim Solodovnik <so...@gmail.com>
wrote:
> Hello All,
>
> Recently I found an article about Wicket in Russian:
> https://habrahabr.ru/company/jugru/blog/345036/
>
> I'm afraid the article is negative :(
>
> The main points are:
> 1) there is lack of developer activity
> 2) Wicket based applications consumes lots of memory
> 3) The performance is bad
> 4) there is no scalability (no cluster support)
>
Like many other Java web frameworks scalability can be implemented
using distributed
data store (like Ignite or Hazelcast) for web session.
I can't read Russian so I don't know which frameworks have been compared to
Wicket but I also agree that these conclusions are (to say the least)
unfounded.
>
> surprisingly #3 is illustrated by the speed of wicket.apache.org
>
> IMO this article lacks numbers and "evidences"
>
> I can try to
> 1) write an article with some numbers to refute this
>
I now it takes a lot of time writing technical articles but it would be
great!
> 2) visit https://2018.jbreak.ru/en/
>
...to face the author of the article :-)???
> ....
>
> WDYT?
>
> --
> WBR
> Maxim aka solomax
>
Re: Article in Russian about Wicket
Posted by Maxim Solodovnik <so...@gmail.com>.
good point :)
On Sat, Dec 23, 2017 at 3:48 AM, Martin Grigorov <mg...@apache.org>
wrote:
> Hi Maxim,
>
> This is not the first article with similar content and most definitely it
> won't be the last one too!
>
> Bad marketing is still better than no marketing!
>
>
> On Thu, Dec 21, 2017 at 5:49 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
> > Hello All,
> >
> > Recently I found an article about Wicket in Russian:
> > https://habrahabr.ru/company/jugru/blog/345036/
> >
> > I'm afraid the article is negative :(
> >
> > The main points are:
> > 1) there is lack of developer activity
> >
>
> Unfortunatelly this statement is not false
> But Wicket is quite mature these days.
> Since 6.x we just stabilize and improve it (only the component queueing
> feature actually broke many things)
> I don't see a need for big refactorings.
>
>
> > 2) Wicket based applications consumes lots of memory
> >
>
> In my last job Tomcat was using -Xmx2g for the peaks. Most of the time it
> was using just 500-600Mb of them.
> For comparison Elasticsearch was setup to use 24Gb per node. And as any
> clustered application you need to run at least 3 nodes ... So Wicket is
> very "cheap" in this regard.
>
>
> > 3) The performance is bad
> >
>
> In my personal experience the bad performance was never because of Wicket.
> Most of the time it is in the database layer (too slow queries or too many
> queries).
>
>
> > 4) there is no scalability (no cluster support)
> >
>
> Yes, there is cluster support!
> Http session replication is supported out of the box by Wicket core.
> There are 5 implementations of clustered data stores in WicketStuff.
>
>
> >
> > surprisingly #3 is illustrated by the speed of wicket.apache.org
>
>
> This site is completely static HTML!
> If this site is slow for him/her/them then most probably any site hosted in
> USA / west Europe is slow too.
>
>
> >
> >
> > IMO this article lacks numbers and "evidences"
> >
> > I can try to
> > 1) write an article with some numbers to refute this
> > 2) visit https://2018.jbreak.ru/en/
>
>
> I'd just ignore the article and spend my time on 1).
>
>
> >
> > ....
> >
> > WDYT?
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
--
WBR
Maxim aka solomax
Re: Article in Russian about Wicket
Posted by Martin Grigorov <mg...@apache.org>.
Hi Maxim,
This is not the first article with similar content and most definitely it
won't be the last one too!
Bad marketing is still better than no marketing!
On Thu, Dec 21, 2017 at 5:49 PM, Maxim Solodovnik <so...@gmail.com>
wrote:
> Hello All,
>
> Recently I found an article about Wicket in Russian:
> https://habrahabr.ru/company/jugru/blog/345036/
>
> I'm afraid the article is negative :(
>
> The main points are:
> 1) there is lack of developer activity
>
Unfortunatelly this statement is not false
But Wicket is quite mature these days.
Since 6.x we just stabilize and improve it (only the component queueing
feature actually broke many things)
I don't see a need for big refactorings.
> 2) Wicket based applications consumes lots of memory
>
In my last job Tomcat was using -Xmx2g for the peaks. Most of the time it
was using just 500-600Mb of them.
For comparison Elasticsearch was setup to use 24Gb per node. And as any
clustered application you need to run at least 3 nodes ... So Wicket is
very "cheap" in this regard.
> 3) The performance is bad
>
In my personal experience the bad performance was never because of Wicket.
Most of the time it is in the database layer (too slow queries or too many
queries).
> 4) there is no scalability (no cluster support)
>
Yes, there is cluster support!
Http session replication is supported out of the box by Wicket core.
There are 5 implementations of clustered data stores in WicketStuff.
>
> surprisingly #3 is illustrated by the speed of wicket.apache.org
This site is completely static HTML!
If this site is slow for him/her/them then most probably any site hosted in
USA / west Europe is slow too.
>
>
> IMO this article lacks numbers and "evidences"
>
> I can try to
> 1) write an article with some numbers to refute this
> 2) visit https://2018.jbreak.ru/en/
I'd just ignore the article and spend my time on 1).
>
> ....
>
> WDYT?
>
> --
> WBR
> Maxim aka solomax
>