[ajug-members] this is funny
rkischuk at gttx.org
Thu Sep 30 11:51:10 EDT 2004
You make a mistake when you attempt to generalize an isolated experience
and use it to say all open source software doesn't have a place in big
companies, or perhaps even in a corporate environment. We have had
terrible experiences with DB2, far worse than what you describe, yet it
would be absurd for me to use that experience to claim that commerical
databases, IBM products, or commercial software aren't worth using.
If anything, this is probably a MyEclipse issue - we use it, and have
seen odd behavior from time to time. In spite of this, it is still well
worth the $30/year. Eclipse itself has always been solid for me, except
in the milestone releases, which can be quirky. I really don't
understand how you drag JBoss in as part of the problem, especially
since you say it's a command-line app, which has nothing to do with J2EE.
I realize you had a problem, and it was frustrating and time consuming.
I can tell you truthfully that I've spent just as much time chasing
nasty glitches in commercial software as I have open source. Internet
Explorer bites me MORE than FireFox/Mozilla. DB2 freaks out on us far
more than PostgreSQL, which just works.
At the end of the day, hey, use what works for you, but implicitly
slamming Eclipse, JBoss, Struts, and Open Source software in general
because of a problem that is probably either due to *commercial
software* (MyEclipse is not OS, AFAIK) or Eclipse (meaning the same
error would probably happen in WSAD under identical circumstances) is
more than a little over the top.
David Wible wrote:
> And I agree with you. You have to look at the whole system - I'm
> using a compaq with 1G of memory, Pentium 4 1.8 GHz.
> It worked fine for 7 weeks and then it just quit. Dunno what
> happened. I don't work for either company and I love wsad from ibm
> and eclipse. I did nothing to my code or config it just quit working.
> But something went wrong. The big companies I'v worked at never
> supported using OS stuff and now I know why. It has its place but
> I've wasted huge amounts of time getting the code to work and inch
> forward. Sure... some of it me but I've never seen a java command
> line call work one moment and then quit the next! Never.
More information about the ajug-members