3 ms·

It sounds like you've never properly programmed in php a day in your life. Stop spouting nonsense. If you're going to develop in php, you do so in strict mode w

It sounds like you've never properly programmed in php a day in your life. Stop spouting nonsense. If you're going to develop in php, you do so in strict mode with all errors turned on. Doing otherwise makes you part of the problem.

TylerE 14y ago
I'll accept this argument when PHP starts shipping with sane defaults. It's only quite recently that register globals got turned off in the default config.
- jtreminio 14y ago
  Global registers were deprecated in 5.3.0, and completely removed in 5.4.0 http://php.net/manual/en/security.globals.php http://php.net/manual/en/security.globals.php 5.3.0 is 2 and a half years old.
  - TylerE 14y ago
    and many shared hosting providers are still on 5.2, and many crappy old scripts require register_globals on.
    - jtreminio 14y ago
      I'm not sure what you're saying here. Are you faulting PHP for versions that are nearly 3 years old? Would you find it a fair comparison if I talked about how bad Rails (framework) is if I was talking about a version that was 3 years old? Every language has its share of horrible programmers. PHP simply makes it easy for those horrible programmers to flourish. Making it easy does not mean the language itself is bad, because when you're ready to stop being horrible, the language is willing and ready to get you out of the muck.
    - shakesbeard 14y ago
      And that's PHP's fault? It won't affect you if you start writing a PHP 5.3 (or even 5.4) app today.
      - TylerE 14y ago
        Yes, it is PHP's fault. It's endemic to the general attitude of the PHP team. "Now just marginally less braindead than every other language" isn't exactly a selling point. Sure, it used to be worse, but I see zero commitment from PHP to actually make real steps to fixing the situation. A real first step would be to start working on a 6.x release that actually removes the gazillion deprecated-but-still-present-and-thus-used things in the language.
  - deleted 14y ago
    [deleted]

TylerE 14y ago

I'll accept this argument when PHP starts shipping with sane defaults. It's only quite recently that register globals got turned off in the default config.

jtreminio 14y ago
Global registers were deprecated in 5.3.0, and completely removed in 5.4.0 http://php.net/manual/en/security.globals.php http://php.net/manual/en/security.globals.php 5.3.0 is 2 and a half years old.
- TylerE 14y ago
  and many shared hosting providers are still on 5.2, and many crappy old scripts require register_globals on.
  - jtreminio 14y ago
    I'm not sure what you're saying here. Are you faulting PHP for versions that are nearly 3 years old? Would you find it a fair comparison if I talked about how bad Rails (framework) is if I was talking about a version that was 3 years old? Every language has its share of horrible programmers. PHP simply makes it easy for those horrible programmers to flourish. Making it easy does not mean the language itself is bad, because when you're ready to stop being horrible, the language is willing and ready to get you out of the muck.
  - shakesbeard 14y ago
    And that's PHP's fault? It won't affect you if you start writing a PHP 5.3 (or even 5.4) app today.
    - TylerE 14y ago
      Yes, it is PHP's fault. It's endemic to the general attitude of the PHP team. "Now just marginally less braindead than every other language" isn't exactly a selling point. Sure, it used to be worse, but I see zero commitment from PHP to actually make real steps to fixing the situation. A real first step would be to start working on a 6.x release that actually removes the gazillion deprecated-but-still-present-and-thus-used things in the language.
- deleted 14y ago
  [deleted]