Opinionated arrogant contentious colleagues,

Keep fighting. I am learning a lot. These are important
considerations.

Newbie

Danny Rubis wrote:
>
> Hey!
>
> Please let's not make this into a battle.  We need to get back to servlet
> issues.
>
> But since you asked I'll include a few.
>
> JTable                  very powerful
> Tabbed Pane        good for organizing
>
> and most of all Object Oriented.  It took me awhile to move from procedural to
> OO and
> then servlets came and now I am back to procedural.
>
> Sans adieu,
> Danny Rubis
>
> kamalnayangsj wrote:
>
> > Hi Danny,
> > If you want a highly interactive site CSS i feel is a better solution than
> > Java Applets.  What kind of interactiveness do you think a CSS cant provide
> > which Java  Applets can?
> >
> > thanks in advance
> >
> > Kamal
> > -----Original Message-----
> > From: Danny Rubis <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > Date: Saturday, October 23, 1999 9:33 PM
> > Subject: Re: Newbie architecture advice needed - servlet/JDBC/applet
> >
> > >Hey!
> > >
> > >Nic, I disagree again.  We have one developer that went the Javascript
> > Servlet
> > >(JS) route.  It took him seven months to complete an interactive product.
> > You
> > >could arguably say to me that he was a lousy / slow programmer.  I can't
> > prove
> > >one way another, except to say that the amount of interactivity that he
> > needed
> > >necessitated reams of JS code.  I took a day looking it over.  With a good
> > IDE
> > >like IBM's VisualAge for Java I can conservatively say that I could have
> > >accomplished the same in about two months.  I would end up with a hunk of
> > code
> > >that was OO as opposed to the JS route, with full power of the Java
> > language
> > >and much easier to maintain.  I agree that for simple interactivity the JS
> > >route is a good quick-and-dirty way, but for anything more than simple
> > products
> > >your best route is applets, IMHO.
> > >
> > >Does anyone have an interactive site using the JS route on the web where I
> > can
> > >go for a look?
> > >
> > >Danny Rubis
> > >
> > >Nic Ferrier wrote:
> > >
> > >> >>> Gary Wesley <[EMAIL PROTECTED]> 10/22/99 10:29:00 PM >>>
> > >>
> > >> >But what if I really need to use Swing
> > >> >(mandated by my boss)?
> > >>
> > >> Get a new boss.
> > >>
> > >> Swing is terrible - you're applet will be terribly slow on just about
> > >> any platform you care to run it on and using the Java Plugin (a must
> > >> for Swing) is like using a shotgun for making pasta.
> > >>
> > >> Seriously.
> > >>
> > >> Swing is a great idea but it just requires too much processing power.
> > >> You'd be much better using AWT if you *have* to go the applet route.
> > >>
> > >> And if you still insist on using Swing the best thing to do is use
> > >> HTTP as the protocol, otherwise you end up with all sorts of firewall
> > >> problems.
> > >>
> > >> But at the end of the day the web just isn't built to work with this
> > >> sort of code. Tiny applets work ok but even then you get problems
> > >> using the plugin. The real power with servlets is to use JSP and
> > >> JavaScript cleverly to make the user *think* they've got something
> > >> truly interactive.
> > >>
> > >> The low resistance of this method is what makes it so cool.
> > >>
> > >> Nic
> > >>

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to