Dance with the one that brung ya
I just read chris fedde's response to Ejecting CGI.pm From the Perl Core, my head nodded in agreement from start to finish. It helped me clarify a few of the thoughts and concerns I've had bouncing around in my head for the past several days.
So here goes: I think it would be a mistake for perl core to not "Dance with the one that brung ya".
How many of us are using Perl because of CGI.pm? When I first got my feet wet with programming it was for the web, using Perl. It was a good month before I got a feel for where perl ended and CGI.pm began. At first they were very much one in the same.
I realize times have changed (tho the title might hint otherwise) I found Mojolicious and haven't looked back. I get a sense that some elite and enlightened (not a dig at EPO) group of "thought leaders" in the community have moved on too. Good for them. I work side-by-side with many, many programmers, sysadmins, and general technologists, that fall back on apache/CGI.pm because they just know it works, and know it's available to them now in their environment. These people may or may never see that distinction between Perl and CGI.pm.
Until we have another de facto standard in place, I say we leave CGI.pm in core. Until that de facto standard is as widely publicized and adopted, I say we leave CGI.pm in the core. It can be a confusing landscape for someone starting out in web programming today. Is abandoning the weekend CGI.pm hacker, and losing them to other languages and frameworks worth the benefits associated to releasing a utopian CGI.pm-free Perl?
How many of those weekend hackers will eventually fall in love with modern perl web frameworks after dabbling under CGI.pm for a while?
I'd bet that far fewer of these weekend/day-job hackers just trying to get a job done will have the opportunity to find and adopt existing modern frameworks if they fail straight out of the gate due to a module or two missing from core. When their expected page doesn't load they'll scratch their heads, then turn to google for how to set up a web site in python or ruby. Besides, they'll think, it's time I looked at something new anyways. Let's hope for their sakes they're lead down another path because a google search for building a web page with perl will be in vein, or frustratingly difficult on a modern perl without CGI.pm in the core.