3 ms·

If you're inherited a legacy project thats a mess then the chances are it was written by some ass who's not following the languages generally accepted PSR stand

by esskay 4y ago

If you're inherited a legacy project thats a mess then the chances are it was written by some ass who's not following the languages generally accepted PSR standards. Proper PHP code is extremely easy to dive into and maintain. The benefit and downside of the PSR standards is they are optional. Sadly some think they know better and opt to roll their own convoluted 'standards' that just end up creating hell for the next person to come along and have to maintain their mess.

cbsjjxhcc 4y ago
PSR isn't generally accepted. It's a bunch of nobody know-it-alls that decided everyone needs to write java in PHP. No thank you.
- ianhawes 4y ago
  You're just wrong. PSRs are widely accepted and all serious frameworks and PHP libraries implement them as needed. I haven't seen a PHP package in quite a long time that didn't implement PSR-4.
  - cbsjjxhcc 4y ago
    Except the largest framework doesn't. And the majority of libraries don't.
    - esskay 4y ago
      What statistics source are you using to determine the 'largest framework' here? Even if we go back to the 2021 Jetbrains developer survey (https://www.jetbrains.com/lp/devecosystem-2021/php/ https://www.jetbrains.com/lp/devecosystem-2021/php/) out of the 11 named frameworks/platforms people are using all but 2 of them use PSR and composer. You keep making these assertations which frankly are coming across as absolute bollocks from someone who's stuck in the early 2000s.
- esskay 4y ago
  If you actually think that you dont know the language very well. It's baked into Composer, all the major frameworks fully use it as to almost every major opensource project that isn't prevented from doing so by legacy code. And honestly if you're a PHP dev intentionally avoiding the widely adopted standards and know someone else is going to have to maintain your code then shame on you.
  - cbsjjxhcc 4y ago
    Composer is trash, semver sucks and I'd tell PSR to go jump but it'd get stuck in a class file somewhere.
    - esskay 4y ago
      You must be a joy to work with. I feel sorry for the rest of your team, having to deal with that kind of view on everything.

by esskay 4y ago

cbsjjxhcc 4y ago

PSR isn't generally accepted. It's a bunch of nobody know-it-alls that decided everyone needs to write java in PHP. No thank you.

ianhawes 4y ago
You're just wrong. PSRs are widely accepted and all serious frameworks and PHP libraries implement them as needed. I haven't seen a PHP package in quite a long time that didn't implement PSR-4.
- cbsjjxhcc 4y ago
  Except the largest framework doesn't. And the majority of libraries don't.
  - esskay 4y ago
    What statistics source are you using to determine the 'largest framework' here? Even if we go back to the 2021 Jetbrains developer survey (https://www.jetbrains.com/lp/devecosystem-2021/php/ https://www.jetbrains.com/lp/devecosystem-2021/php/) out of the 11 named frameworks/platforms people are using all but 2 of them use PSR and composer. You keep making these assertations which frankly are coming across as absolute bollocks from someone who's stuck in the early 2000s.
esskay 4y ago
If you actually think that you dont know the language very well. It's baked into Composer, all the major frameworks fully use it as to almost every major opensource project that isn't prevented from doing so by legacy code. And honestly if you're a PHP dev intentionally avoiding the widely adopted standards and know someone else is going to have to maintain your code then shame on you.
- cbsjjxhcc 4y ago
  Composer is trash, semver sucks and I'd tell PSR to go jump but it'd get stuck in a class file somewhere.
  - esskay 4y ago
    You must be a joy to work with. I feel sorry for the rest of your team, having to deal with that kind of view on everything.