> Unfortunately, 'beans' have now caught on the the enterprise > managers' mind (whatever that is) and thats all that they > can think of, or ask for on resumes. So sticking with 'beans' > means you don't have to try to re-educate a mind set. > (Which I've found to be impossible. Just look at the 'hacker' > vrs. 'cracker' issue if your not convinced.)
I'm in favor of tipping the hat to Java and using "beans" to describe standard components. Most developers know what you mean. However, then we have to distinguish between Perl Beans and Java Beans, unless they both use the same coding conventions. -- Raul Nohea Goodness [EMAIL PROTECTED]
