Martin Cooper wrote:
On Sat, 20 Mar 2004, Nadeem Bitar wrote:
On Sat, 2004-03-20 at 17:47 -0500, Ted Husted wrote:
On Fri, 19 Mar 2004 18:53:58 -0800, Nadeem Bitar wrote:
If for example JSF 2.0 is available, and Spring Framework is well
integrated with JSF before Struts 2.0 is available, I strongly
believe that struts won't have a place and would lose market shares.
First let's be very clear.
It's *not* about "market share".
I have to disagree with you on this one. Struts is the defacto standard
because of its market share. It is well documented, it has a healthy
community, and struts talent is available easily, because of its market
share.
I think what Ted is trying to say is that the Struts developers do not
work on Struts to increase its market share, but because Struts works for
us, and we care to put in the time and effort to maintain and further
develop it. The fact that it has become sufficiently popular to turn into
a de facto standard is nice, but that's secondary to (most of) us, and not
why we're here.
--
Martin Cooper
Yes. This has been true right from the beginning.
Struts does not need market-share to survive. All we need is a community of developers who use the product and want to help support it.
A community of developers would support a product only if they believe
in it. Many hard core struts users and developers are migrating to other
frameworks and this is a loss for the whole community. Struts 2.0 would
have a chance to bridge the gap between struts and other frameworks.
Since Struts 2.0 is still on the drawing board I am only advocating to
do it right even if that means breaking backward compatibility and
making major architecture changes.
You are right on the target. With the current thinking of either Struts
1.3 or Struts 2.0, i think Struts will be a de-facto standard of web
controller for other frameworks and contaiers.
BaTien
DBGROUPS
How many downloads we realize isn't important. Whether 90% or whether 10% of shipping applications use Struts isn't important. What's important is that Struts works well for the people who do want to use it, and that those people want to do the work to make it better.
Of course, if we all find that JSF does most of what we all need, and we want to use it in our own applications, then Struts will quickly become whatever other JSF components we need to ship our own applications. But so long as products like JSF leave out components that real-life applications need, there will always be a Struts. From the beginning, it's always been about providing axles between the wheels that Java already has.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
