You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Andrea Del Bene <an...@gmail.com> on 2013/07/31 13:56:09 UTC
Interesting article from Zeroturnaround
I don't agree with everything in it, but it's a good article anyway :) ...
http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Interesting article from Zeroturnaround
Posted by Michael Mosmann <mi...@mosmann.de>.
Am 31.07.13 19:24, schrieb Igor Vaynberg:
> unless youve built and maintained a real non-trivial application using all
> those frameworks how can you put numbers on them?
I used Grails,Wicket,JSF,Spring Webflow and Struts in real non-trivial
applications. I was involved in projects using GWT and JSF. I played
around and talked with many other developers about Play and Vaadin. And
still the only thing i have is an opinion about it:)
But to put numbers on it, i can show where i see differences. And not
only my numbers are different.. i put them on different places. I hope i
can show my experience a little bit more quantified ..
Its an opinion, not facts. In i will not put something in order.. such
as "the winner is.. " because i think this is kind of useless.
> -igor
>
>
> On Wed, Jul 31, 2013 at 5:47 AM, Michael Mosmann <mi...@mosmann.de> wrote:
>
>> Am 31.07.13 13:56, schrieb Andrea Del Bene:
>>
>> I don't agree with everything in it, but it's a good article anyway :) ...
>>> http://zeroturnaround.com/**rebellabs/the-curious-coders-**
>>> java-web-frameworks-**comparison-spring-mvc-grails-**
>>> vaadin-gwt-wicket-play-struts-**and-jsf/<http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/>
>>>
>> I will take some time and put my own numbers (with some hopefully good
>> explanations) in to the mix. So stay tuned:)
>>
>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Interesting article from Zeroturnaround
Posted by Igor Vaynberg <ig...@gmail.com>.
unless youve built and maintained a real non-trivial application using all
those frameworks how can you put numbers on them?
-igor
On Wed, Jul 31, 2013 at 5:47 AM, Michael Mosmann <mi...@mosmann.de> wrote:
> Am 31.07.13 13:56, schrieb Andrea Del Bene:
>
> I don't agree with everything in it, but it's a good article anyway :) ...
>>
>> http://zeroturnaround.com/**rebellabs/the-curious-coders-**
>> java-web-frameworks-**comparison-spring-mvc-grails-**
>> vaadin-gwt-wicket-play-struts-**and-jsf/<http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/>
>>
> I will take some time and put my own numbers (with some hopefully good
> explanations) in to the mix. So stay tuned:)
>
>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Interesting article from Zeroturnaround
Posted by Michael Mosmann <mi...@mosmann.de>.
Am 31.07.13 13:56, schrieb Andrea Del Bene:
> I don't agree with everything in it, but it's a good article anyway :) ...
>
> http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/
I will take some time and put my own numbers (with some hopefully good
explanations) in to the mix. So stay tuned:)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Interesting article from Zeroturnaround
Posted by Bernard <bh...@gmail.com>.
Simon's article is entertaining but of low quality.
It contains a few errors.
Wicket received negative points certainly for the wrong reasons.
I don't know what Simon tries to address with his criticism of
Wicket's inheritance. Designing a web site based on markup inheritance
could be considered difficult to grasp. But that is optional and I
don't think he even tried to get there. He does not comment on whether
other frameworks even provide this. Unfortunately he used this in
multiple rating criteria.
But he did not mention markup composition and dynamic component
replacement which in Wicket is very easy.
Components have to extend Wicket's basic components like Panel. This
is easy. Not understanding this concept easily would be a concern.
His comments on scalability are not convincing. He does not
distinguish between performance and scalability. Wicket has a slight
scalability disadvantage because of its reliance on session affinity
which he did not mention. Wicket generates content on the server like
Grails, Struts, Spring MVC, Play and JSF. GWT and Vaadin are more
client centric. So he would have to group client side and server side
frameworks to clarify.
"Wicket works well for scalability if that is your goal when
developing the foundation; otherwise, youre better off using another
framework that doesnt have such a huge server resource consumption
problem."
This sentence is nonsense, semantically and technically. It
disqualifies the whole article.
He would need to clarify what his "foundation" is and provide a
scenario to back up his claim of "huge server resource consumption
problem".
I think it is quite difficult to rate Web frameworks, especially when
they are based on different architectures, and have different
purposes.
Bernard
On Wed, 31 Jul 2013 13:56:09 +0200, you wrote:
>I don't agree with everything in it, but it's a good article anyway :) ...
>
>http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org