Technological inertia is hard to fight
wicket is building momentum required to handle struts' inertia, give it
time. I was going to ask the wicket leads to give us a graph showing
wicket's growth generally especially checking download figures this year
against last year and mailing list figures...
On 5/24/07, Marc Stock <[EMAIL PROTECTED]> wrote:
The company I'm currently working at is a Struts 1 shop. Like most
companies, they tend to stick with technologies they know even if they are
inferrior. Right now I'm working on a Wicket prototype for them but it is
likely they will stay a Struts shop. Technological inertia is hard to
fight. It's a million times easier for a company to find Struts resources
than Wicket (or virtually any other framework) resources. However, that
is
an extremely shortsided way to evaluate switching frameworks. For
example,
lets say they have to train everyone they hire because they can't find
people with Wicket experience. In my experience, it's taken me about two
weeks to get up to speed on Wicket. I'm no expert yet but I think I have
a
pretty good foundation and most of my questions about the framework are
regarding more advanced problems involving Ajax. So the cost to the
company
so far has been two weeks of me learning Wicket (from knowing nothing at
all). Now, the prototype that I have so far would have probably taken me
at
least two weeks in Struts 1 and I already know Struts 1 very well. The
difference in productivity between the two frameworks is pretty dramatic.
Wicket is simply far superior for the typical website. About the only
time
I wouldn't consider Wicket is for high volume websites like Amazon.com,
etc.
However, they don't even use Java either.
I say all this because you're biggest problem will be this inertia and
they
will resist any change even if the technology is much better simply
because
people are too lazy to learn new things. Make sure they understand that
there's far more to consider than the initial learning period and that
long
term productivity must be evaluated to make an educated decision.
So far my biggest complaint about Wicket is the documentation is scattered
around the wiki and you basically have to learn it by studying example
code.
It's unfortunate that such a cool framework is so lacking
documentation. I
would recommend buying Pro Wicket. It's not super comprehensive but it's
a
lot better than nothing. Wicket In Action is in progress but not
completed
yet but I'm sure that will be a great addition and maybe fix a lot of the
documentation weaknesses.
Florian Hehlen-2 wrote:
>
> Hi,
>
> Thanks for the feedback. We are contemplating doing some prototyping. I
> am currently implementing a small application within the group with
> wicket but it is not clear weather we will have the time to do the same
> for struts. On the other hand most people in the group have some level
> of experience with struts.
>
> When is 1.3 being released?
>
> regards,
> florian
>
> Johan Compagner wrote:
>> can't you make 2 prototypes of the same application with your team and
>> then see how it works?
>>
>>
>>
>> 3-Objectively, I am also looking for what wicket is weak at.
>>
>>
>>
>> hope you have a magnifying glass with you then because that is
>> ofcourse hard to find ;)
>> But most people would say i guess use of session memory. But we manage
>> that for you
>> and in 1.3 this is much lighter then before. And i have seen struts
>> apps that did take
>> 1MB of session memory and most of the time that where also leaks
>> because of session objects
>> that wheren't cleaned correctly because the developer needed some
>> state from Page X to Page Y.
>> but forgot to clean it up or the user never got to Page Y.
>>
>> johan
>>
>>
------------------------------------------------------------------------
>>
>>
-------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wicket-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
--
View this message in context:
http://www.nabble.com/wicket-vs.-struts-presentation-tf3795289.html#a10790427
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
