I'll add my 2cents because my useage perspective is slightly different
from most. I recently (2+ months ago) accepted my current position as
software architect and I kinda recieved ownership of a web architecture
that utilizes Webware. So I didn't get to really choose to use it.=20
However, I've reimplemented our web architecture over it so that its
easier on our page authors, Human Experience designer and developers
responsible for supporting those people and I've been pretty pleasantly
surprised and happy with what Webware does for us.
There are tiny things that I'd like to tweak and alter but nothing major.=
I've been satisfied with performance, useage and documentation of webware
We use webware and webkit with Cheetah templates (not really my first
choice, but effective and useful overall as well), so that might give you
an idea of the model we employ here. We're working with the last officia=
release, so I've found at least one bug and after this list was able to
assist me in identifying the issue at hand found that the bug had already
been identified and fixed in the 'tips' of the cvs module for webkit.
This is my first architectural position involving python so I was unverse=
in the options that were out there, and my boss coming in made it clear h=
didn't want to get rid of webware (we have legacy code that works as is
and no time to completely replace it to support a new engine), so I don't
know what you're up against in terms of alternatives, but the bottom line
is that Webware seems to be a living product with a reasonable size and
helpful user base. This list is one that I watch actively everyday.
hope this is useful data for you,
> Hi Matt,
> Thanks for taking the time and effort to reply (and quickly!) and for
> your helpful comments. It is very useful to know that "the reason that
> there aren't many bug fixes is that there aren't many bugs".
> Considering that there aren't many bugs and that it is stable, would
> it be logical, even easy, to upgrade the status from Beta to GA, (e.g.
> doing a new release with version number 1.xx)? This would
> a) reflect confidence in the Webware's stability
> b) encourage take-up and widen the user base
> c) incorporate improvements into the release which are currently only
> accessible via cvs (as suggested by lloyd in his follow-up message to
> your reply).
> Considering what I have discovered regarding frameworks, there is a
> great need (for oddies like me, anyway :D ) for a _good_ n-tier web
> framework alternative to J2EE (powerful, but too heavyweight for my
> needs). If Webworks has the stability, then perhaps it is the one (no
> pun intended, Matrix fans) : perhaps a GA release would give Webworks
> wider recognition...? promotion...? acceptance...?
> Anyway, your confidence has encouraged me to give it a try (sort of
> Thanks again for your reply and info.
> On Wed, 27 Oct 2004 16:54:57 -0400, you wrote:
>>I'm not one of the developers, but I've been using webkit nearly
>>exclusively for almost 3 years.
>>I think that part of the reason that there aren't many bug fixes is tha=
>>there aren't many bugs. The bugs that are found tend to be pretty
>>simple, and I've seen them get resolved quickly. I think that it's a
>>testament to the simplicity of the framework.
> -- snip --
>>I wouldn't say that it has gone through a quiet time or is being
>>renewed; nor would I say that it's stalled. I'd say that it's just
>>chugging along nicely. I'd say that the history of this list is a good
>>barometer, really. Just because therethere aren't many bugs is no
>> "progress" doesn't mean that
>>the code doesn't work. For example, I bet that the core GNU utils don't
>>have many bug fixes, but they're in heavy use ;-)
>>There have been some similar questions to yours lately; you may benefit
>>from reading the responses to them also.
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> Webware-discuss mailing list