Re: RFC: ext/mysql deprecation

hi, On Tue, Nov 13, 2012 at 7:29 PM, Ronald Chmara <ronabop@gmail.com> wrote: > On Tue, Nov 13, 2012 at 8:28 AM, Arvids Godjuks > <arvids.godjuks@gmail.com> wrote: >> It took me like 10 minutes of "Search & Replace" in my IDE to make a switch >> to mysqli and a few more hours to validate that everything is ok and catch >> places where search & replace failed. The amount of work is overestimated, >> especially if you have a regexp capable search & replace. > > 10 minutes x 50 billion > (http://www.statisticbrain.com/total-number-of-pages-indexed-by-google/ > ) is not a trivial number. Heck, assume even only 10% of the web pages > on the internet use mysql_* calls, and you're still talking 50 billion > minutes, or about 95 thousand years. At 1%, it's only 9 thousand > years, possibly greater than the entire written and recorded history > of the human race. > > Considering there are a huge quantity of PHP end users (Drupal, > Joomla, Wordpress, Magento, etc.) who don't even know what 'regexp' > means, and would take a lot more time than ten minutes just trying to > understand why "my website is broken, can you fix it?".... yeah. > > On the less pessimistic side, since I work as a PHP site > author/maintainer for a living, a pool of 9,000 years of work would > suit me just fine. Even 900 years would equate to a huge jobs program > for my field. Can we stop about arguing about the removal? It is not happening and won't until 6+. We are talking about adding a E_DEPECRATED notice, nothing else. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org