R
Ryan Stewart
Yes. As has been stated by myself and others, including the post you repliedBrian Kildea said:I understand your point, but I think the answer here is very much dependent
on one's requirements. For example, I don't develop sofware for use by
100,000 "visitors". My applications are used by a very small community of
specialists, and there is on-line help, users manuals and training courses
that are developed to accompany the application. Many in this community
wrongly assume that every other project is just like theirs meaning that
*everyone* is writing applications for the whole Internet user base.
I will admit to having a preference for Swing. Some of it has to do with my
feeling that I can develop richer, more intuitive interfaces with Swing than
I can with what's available in a browser. That can serve my clients well --
maybe not everyone's, but mine. I also spent endless hours 3 years ago
trying to work around slight variations in browsers, and their Javascript
bugs that remained unfixed for many versions. I also hated the continuous
conversion between Javascript, HTML forms and server side "languages",
complicated by the lack of strong typing in any of these technologies. I
can do more than twice as much in half the time with Java and Swing and
create a much more bug free application. Surely one can argue that that
best serves the client -- in my case the paying client and the operators are
not the same. I think I serve them both well in this regard.
to, requirements should determine your tools. This thread started with Mr.
Eamer asking whether we would choose Swing or some web-based technology. My
answer is yes. I would choose one or the other based on what I'm expected to
develop. (Possibly something else, but these cover our needs pretty well at
the moment.)
As an aside, how is JSP any less strongly typed than Java? Oh, wait. You
said it's been 3+ years since you worked with web-based applications? Check
out some of the new stuff. At least give JSP a look.