OK. Should have stuck a wink in there. Urge to kill fading . . . fading . . . fading . . . RISING!!!! . . . fading . . . fading . . .
gone. ;-) Erik -----Original Message----- From: "Frank W. Zammetti" <[EMAIL PROTECTED]> Sent: Aug 10, 2005 3:38 PM To: Struts Users Mailing List <user@struts.apache.org> Subject: Re: Nice try (was Java code generator including Struts 1.2) Hey, back the testosterone truck up Erik... You want to disagree with the opinion? Fine, no problem. I don't think Swing is especially good. Show me where I'm wrong, I'll listen. No need to attack someone over something as trivial as saying some technology sucks... unless you created that technology, and even then it wouldn't be terribly appropriate. Frank [EMAIL PROTECTED] wrote: > What a load of crap. > > Swing doesn't suck, you just suck at it. > > Erik > > > -----Original Message----- > From: Michael Jouravlev <[EMAIL PROTECTED]> > Sent: Aug 10, 2005 1:59 PM > To: Struts Users Mailing List <user@struts.apache.org> > Subject: Re: Nice try (was Java code generator including Struts 1.2) > > On 8/10/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > >>I remember having to deal with some Swing code that was created by a >>junior programmer using some IDE (I forget which frankly, it's not on the >>market any more - I want to say it was IBM's old one before WSAD, but I >>might be wrong). The code was such an immense tangle of crap it still >>makes me shudder to think of it all these years later. > > > The original problem is that Swing does not have resource files. > Apparently, Swing designers thought that Swing apps would have been > fluid and resizable, and it would have been hard to stick all fluidity > into a simple resource file. And now you have it. Swing code is crap > even when it is well-formatted, with these unwieldy listeners and a > forest of interfaces. There are nicer ways to create event listener > than to implement an interface with bunch of methods in it. > > And now we are switching to "why programming to interfaces" thread. > Swing is a clear example why programming to interfaces is sometimes > such a pain in the butt. > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
