On 30 July 2014 17:42, Jarkko Hietaniemi <jhi@iki.fi> wrote: > On Wednesday-201407-30, 11:28, demerphq wrote: > >> I personally think that we include things we shouldn't and dont include >> things we should, and that the discussion cannot be simplified to >> "minimal core is better". >> > > The problem with "more is better" approach is that the answer to "what is > more" depends on the developers you ask, and the current fad. Does anyone > still remember how SOAP was supposed to be the best thing since sliced > bread? There was talk of including SOAP into the core. (And to be fair > and balanced, also including XML-RPC.) Group of developers, let's call > them X, will want all XML utils. But group Y absolutely needs CSV support, > while group Z can't live without a distributed robust high-performance > message bus solution. No matter how wide we stretch the "more", it will > not be enough. Until it's CPAN. > > Yes, I am familiar with this line of reasoning. However, when I think that the only reliable way to find out the type of a reference, or that an object is blessed is loading a CPAN module I think that it misses a key point. Ditto for simple utilities like "sum", and "max" and whatnot. My personal feeling is that there are things that are more or less "application" level that should not be part of Perl core, and there are things on CPAN which should have been part of the language from the beginning. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next