good point :) On Sat, Dec 23, 2017 at 3:48 AM, Martin Grigorov <[email protected]> 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 <[email protected]> > 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
