Another opinion. We've been very satisfied with what Witango has been
able to offer in terms of rapid development and, lately, stability
and speed. (Mac OS X Server 10.3.9, Oracle 9i, Witango 5.5, J2EE
Witango servlet). Yes, there HAVE been issues esp with the Mac dev
studio, and yes, Witango 5.5 is not perfect, but actually I have
found few if any programs that are perfect - there's always
something, it seems, either in lack of functionality one would like,
or some problems.
I am under the impression that Phil and his team are extremely
focussed on getting Witango 6 (a complete re-write) to market, and
have to admit that I am just waiting as patiently as I can for this
to happen, as I feel that many of the remaining issues that have been
bothersome will evaporate when that happens. In the mean time,
Witango is doing just great for us in a small, yet enterprise-wide
application (designated Tactical importance) at the US federal level.
When asked by anyone what platform we run, we dodge the admittedly
frustrating lack of visibility of Witango by stating we're running on
J2EE with an Oracle backend. Satisfies the audience in a very
positive way and we can get down to more substantive issues of what
enhancements or improvements are needed.
We *are* exploring ancillary functionalities that can be used to
enhance what Witango offers, such as AJAX and Ruby on Rails, but
that's at the presentation layer, so it's a whole 'nother critter.
I'd much rather see discussions of such intersecting technologies
than replacement ones, as these are more useful to us.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
