Jason W. May wrote: > Now we're getting to something actionable. Indeed. And the best part is that they can be pursued orthogonally. > 2. better shareability of components. Something more/different than > CPAN provides today. I still don't understand what this really means. J2EE comes from a single vendor. What "shareability" are you referring to as a model? And if you're just talking about shareability of components in general, there isn't anything better than CPAN, anywhere. -- John Porter Science class should not end in tragedy.
- Re: Let perl be Perl (was... perl vs php) Abigail
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- Re: Let perl be Perl (was... perl vs php) Abigail
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- Re: Let perl be Perl (was... perl vs php) Abigail
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- Re: Let perl be Perl (was... perl vs php) Chris Nandor
- RE: Let perl be Perl (was... perl vs php) Jason W. May
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- Re: Let perl be Perl (was... perl vs php) Jason W. May
- Re: Let perl be Perl (was... perl vs php) John Porter
- Re: Let perl be Perl (was... perl vs php) Chris Winters
- Re: Let perl be Perl (was... perl vs php) Abigail
- Re: Let perl be Perl (was... perl vs php) Rodney Clang
- Re: Let perl be Perl (was... perl vs php) John Porter
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- RE: Let perl be Perl (was... perl vs php) Selena Sol
- Re: Let perl be Perl (was... perl vs php) John Porter
- Re: Let perl be Perl (was... perl vs php) Nathan Torkington
