4 ms·

isn't that ... too soon? the main reason i use PHP is because there is no time to rewrite stuff.

onli 7y ago
Yes. It makes those types of projects increasingly difficult to support further.
bovermyer 7y ago
PHP 5 has been deprecated for several years now. PHP 7.0 was released in 2015, almost five years ago. The current version is PHP 7.3. While upgrading from PHP 5.4 or lower to 7 can be... interesting, it's not all that difficult or time-consuming. PHP 5.5 or higher to 7 is much easier.
- Fogest 7y ago
  We personally struggle to just keep Ubuntu updated with LTS releases, let alone managing all the updates to ensure software works on the new packages installed on whatever LTS version. The issue is that when you have smaller companies with small web development departments you end up with a lot of differents sites/tools made over time. So now when it comes upgrade time you have a large pile of stuff that needs upgrading. One developer making new websites over a few years time isn't that crazy, so unfortunately you end up with a build-up of projects to update. Yet while having time pressures to update, you also have pressures to continue to work on new things or fixing problems users have reported. It usually comes down to time/money. Unfortunately dedicating time to updating things is never as high of a priority as making new things, adding new features, or fixing bugs. Because it follows the traditional mindset of it's working, why update it.
  - dehrmann 7y ago
    > We personally struggle to just keep Ubuntu updated with LTS releases This is a little like having the money to buy a hand-made car, but only being able to afford ever other oil change.
  - bovermyer 7y ago
    I get it. I'm a consultant, so I'm familiar with code bases that are a little...well-worn. If the business decides the risk is acceptable, then that's fine. As an engineer, you're supposed to communicate and document the risks associated with technical decisions. After that, if your employer decides Technology X.Y is good enough, then accept it and move on. You made your case, and the business considered it and made a choice.
    - Fogest 7y ago
      The risks are usually known, the problem is more that it's a slow process to get everyone to update their stuff and have it ready for new versions of whatever languages and tools they are using.

onli 7y ago

Yes. It makes those types of projects increasingly difficult to support further.

PHP 5 has been deprecated for several years now. PHP 7.0 was released in 2015, almost five years ago. The current version is PHP 7.3. While upgrading from PHP 5.4 or lower to 7 can be... interesting, it's not all that difficult or time-consuming. PHP 5.5 or higher to 7 is much easier.

Fogest 7y ago
We personally struggle to just keep Ubuntu updated with LTS releases, let alone managing all the updates to ensure software works on the new packages installed on whatever LTS version. The issue is that when you have smaller companies with small web development departments you end up with a lot of differents sites/tools made over time. So now when it comes upgrade time you have a large pile of stuff that needs upgrading. One developer making new websites over a few years time isn't that crazy, so unfortunately you end up with a build-up of projects to update. Yet while having time pressures to update, you also have pressures to continue to work on new things or fixing problems users have reported. It usually comes down to time/money. Unfortunately dedicating time to updating things is never as high of a priority as making new things, adding new features, or fixing bugs. Because it follows the traditional mindset of it's working, why update it.
- dehrmann 7y ago
  > We personally struggle to just keep Ubuntu updated with LTS releases This is a little like having the money to buy a hand-made car, but only being able to afford ever other oil change.
- bovermyer 7y ago
  I get it. I'm a consultant, so I'm familiar with code bases that are a little...well-worn. If the business decides the risk is acceptable, then that's fine. As an engineer, you're supposed to communicate and document the risks associated with technical decisions. After that, if your employer decides Technology X.Y is good enough, then accept it and move on. You made your case, and the business considered it and made a choice.
  - Fogest 7y ago
    The risks are usually known, the problem is more that it's a slow process to get everyone to update their stuff and have it ready for new versions of whatever languages and tools they are using.