6 ms·

So you are blaming PHP's excellent backward compatibility. Why I am not surprised? :)

fiedzia 10y ago
I just oppose naming it "brand new". Its largely still just as broken as it always was. Fixing one issue per release will maybe get PHP to state comparable with other languages somewhere in the next century (if they stand still in the meantime). Also PHP could easily add sane new stdlib if it wanted to, and keep supporting the old one as long as people want to. I just don't think anyone is really interested in doing so. Most PHP users don't care much, and few large companies that fund the work are mainly focused on keeping the ship from sinking.
- NormlOverrated 10y ago
  >I just don't think anyone is really interested in doing so. Most PHP users don't care much They care. They are interested. But backwards compatibility is a huge issue. PHP7 is much better, it's faster, it uses less resources, and yet you still have hosts running PHP 5.3, some even running 5.2! How do you combat a crowd like that? I don't want PHP to get stuck in IE6 mode, and I sure hope the community voices their valid criticism and takes action.
  - fiedzia 10y ago
    > They care. They are interested. Have they really been, PHP issues would be fixed long time ago. It had 7 major releases, and people complain about exactly the same things. All the people I know who complain about it and switch to something else say the exact same things, no matter what PHP version they've left behind. Those who do care simply go somewhere else, only those who do not or have massive codebase to support stay. > PHP7 is much better Lets agree to disagree on that. Its not better enough to draw any of PHP opponents to it. > you still have hosts running PHP 5.3, some even running 5.2! How do you combat a crowd like that? You don't. Let them be. There are people using PHP 1,2,3 and 4 somewhere out there. They may never switch. Why should it hold back the rest of the world? > I don't want PHP to get stuck in IE6 mode The whole PHP is its own IE6.
    - dreistdreist 10y ago
      Taking into considering that the thing you complained about (errors instead of exceptions) was fixed in PHP 7, maybe you should reevaluate your opinion about PHP not fixing things in newer versions...
- colshrapnel 10y ago
  "keeping the ship from sinking" - surely you are a borad member for Facebook, Badoo, Dailymotion. I appreciate your first hand evidence. Come on, if a handful inconsistent function names is all the problem with PHP to you, let me suggest you to get yourself a good IDE with a code completion feature. You'll forget that "broken stdlib" forever... of course if your aim is to get the job jone, not to slander a language you aren't working with.
  - fiedzia 10y ago
    That they are inconsistent is one problem. That they are functions is another (in otherwise object-oriented language). That they don't throw exceptions is one more (in a laguage that has them). IDE won't fix any of that.
    - colshrapnel 10y ago
      You can make them throw actually. set_error_handler("myErrorHandler"); function myErrorHandler($errno, $errstr, $errfile, $errline) { throw new Exception($errstr, $errno); } Is all you need. They are functions - yes. If your first language was fully OOP, then probably PHP is not your language of choice. It doesn't make it bad, though.
      - babyrainbow 10y ago
        >set_error_handler("myErrorHandler"); function myErrorHandler($errno, $errstr, $errfile, $errline) { throw new Exception($errstr, $errno); } Is all you need. So you think boxing all kinds of errors into one generic exception type is a solution to this shortcoming of the language? That sure feels like a 'php' solution. I will give you that. But that ain't pretty (even as a work around), and no, it does not do the job. May be if you don't know how to work with exceptions in the first place, then it might work for you. But you might end up with a code base like this [1] [1] http://stackoverflow.com/questions/3425835/converting-errors-to-exceptions-design-flaw http://stackoverflow.com/questions/3425835/converting-errors...
      - fiedzia 10y ago

I just oppose naming it "brand new". Its largely still just as broken as it always was. Fixing one issue per release will maybe get PHP to state comparable with other languages somewhere in the next century (if they stand still in the meantime). Also PHP could easily add sane new stdlib if it wanted to, and keep supporting the old one as long as people want to. I just don't think anyone is really interested in doing so. Most PHP users don't care much, and few large companies that fund the work are mainly focused on keeping the ship from sinking.

NormlOverrated 10y ago
>I just don't think anyone is really interested in doing so. Most PHP users don't care much They care. They are interested. But backwards compatibility is a huge issue. PHP7 is much better, it's faster, it uses less resources, and yet you still have hosts running PHP 5.3, some even running 5.2! How do you combat a crowd like that? I don't want PHP to get stuck in IE6 mode, and I sure hope the community voices their valid criticism and takes action.
- fiedzia 10y ago
  > They care. They are interested. Have they really been, PHP issues would be fixed long time ago. It had 7 major releases, and people complain about exactly the same things. All the people I know who complain about it and switch to something else say the exact same things, no matter what PHP version they've left behind. Those who do care simply go somewhere else, only those who do not or have massive codebase to support stay. > PHP7 is much better Lets agree to disagree on that. Its not better enough to draw any of PHP opponents to it. > you still have hosts running PHP 5.3, some even running 5.2! How do you combat a crowd like that? You don't. Let them be. There are people using PHP 1,2,3 and 4 somewhere out there. They may never switch. Why should it hold back the rest of the world? > I don't want PHP to get stuck in IE6 mode The whole PHP is its own IE6.
  - dreistdreist 10y ago
    Taking into considering that the thing you complained about (errors instead of exceptions) was fixed in PHP 7, maybe you should reevaluate your opinion about PHP not fixing things in newer versions...
colshrapnel 10y ago
"keeping the ship from sinking" - surely you are a borad member for Facebook, Badoo, Dailymotion. I appreciate your first hand evidence. Come on, if a handful inconsistent function names is all the problem with PHP to you, let me suggest you to get yourself a good IDE with a code completion feature. You'll forget that "broken stdlib" forever... of course if your aim is to get the job jone, not to slander a language you aren't working with.
- fiedzia 10y ago
  That they are inconsistent is one problem. That they are functions is another (in otherwise object-oriented language). That they don't throw exceptions is one more (in a laguage that has them). IDE won't fix any of that.
  - colshrapnel 10y ago
    You can make them throw actually. set_error_handler("myErrorHandler"); function myErrorHandler($errno, $errstr, $errfile, $errline) { throw new Exception($errstr, $errno); } Is all you need. They are functions - yes. If your first language was fully OOP, then probably PHP is not your language of choice. It doesn't make it bad, though.
    - babyrainbow 10y ago
      >set_error_handler("myErrorHandler"); function myErrorHandler($errno, $errstr, $errfile, $errline) { throw new Exception($errstr, $errno); } Is all you need. So you think boxing all kinds of errors into one generic exception type is a solution to this shortcoming of the language? That sure feels like a 'php' solution. I will give you that. But that ain't pretty (even as a work around), and no, it does not do the job. May be if you don't know how to work with exceptions in the first place, then it might work for you. But you might end up with a code base like this [1] [1] http://stackoverflow.com/questions/3425835/converting-errors-to-exceptions-design-flaw http://stackoverflow.com/questions/3425835/converting-errors...
    - fiedzia 10y ago