Java is non-free. It should be avoided like the plague, or alternatives like gcj (GNU java complier), kaffe, and the like should be used. All of these have very limited awt/swing support, however. GCJ does allow compiling to native code, which is important if you ever want a java application to be less than painfully slow (anyone tried using Limewire lately?). Until it matures, let's just leave java in the server-applet realm where it seems to belong. Just my $.02. Ryan On Mon, 2003-04-28 at 09:01, Matt Thoren wrote: > Java swing is NOT a terrible UI. It is easy to use and deploy. I > wrote an app one-time and deployed it on Compaq Tru64, OpenVMS, > NT/2000, Solaris and on Linux without modification. > > The JTable class alone is enough of a reason to use swing. It is > very easy to create a front end to a database with JDBC. > > Finding people to maintain and support a deployed app is easy as most > college level courses include java. > > Java is easy to use, lots of documentation and examples, easy to > deploy, easy to maintain. That is why it is popular. This is why > I suggest to my clients -- and many of my clients have this in place > already -- that all new code be written in Java and any migration > should be done to Java. > > Matt Thoren > mthoren at mttcc.com -- Ryan Hayle <hackel at walkingfish.com> _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list