3 ms·

The amount of legacy applications being run on the internet is huge. Breaking stuff would put a great financial burden on the companies running those. It is a

by gog 7y ago

The amount of legacy applications being run on the internet is huge. Breaking stuff would put a great financial burden on the companies running those. It is a sensible approach IMHO. What kind of bad stuff are you talking about? If you talk about function names and parameter ordering not being consistent that is not an issue for developers using the language daily, most of them are using an IDE so it doesn't matter as much as people who don't use it say.

pdimitar 7y ago
Those legacy applications won't ever be upgraded to that theoretical and slimmed down PHP anyway, so I don't see a problem.
- simion314 7y ago
  Old PHP projects can be upgraded in the present because backwards compatibility exists, as i metnioend in other comment I done such a small upgrade and I hat to change only 1 deprecated function with a different one. If this would not have been possible the project would have still be running on an old version without security fixes and slower(eating more electricity so bad for environment)
  - pdimitar 7y ago
    If you say so. ~5 years ago I had to work a full week, 8h a day, to fully upgrade a medium-sized website from PHP 5.2 to 5.4, and eventually gave up. Most of the time was spent trying to cope with different datetime parsing idiosyncrasies.
    - simion314 7y ago
      I am sorry you had such a bad experience, can I ask you to give me some link or details about your issues with datetime , I want to learn about the problems I do not doubt you. I had some problems with mysql updates though, new versions had different)better default behavior). we were using an ORM for the project but the initial setup and migrations were made in plain SQL and those needed to be updated. As an example in older mysql you could have a timestamp column NULL with no default value set and now we needed to fix to set a curenttime as default.
johnday 7y ago
> If you talk about function names and parameter ordering not being consistent that is not an issue for developers using the language daily It does feel like this is analogous to saying "the holes in the floor of our building aren't an issue - all the senior devs know where they are by now"

by gog 7y ago

pdimitar 7y ago

Those legacy applications won't ever be upgraded to that theoretical and slimmed down PHP anyway, so I don't see a problem.

simion314 7y ago
Old PHP projects can be upgraded in the present because backwards compatibility exists, as i metnioend in other comment I done such a small upgrade and I hat to change only 1 deprecated function with a different one. If this would not have been possible the project would have still be running on an old version without security fixes and slower(eating more electricity so bad for environment)
- pdimitar 7y ago
  If you say so. ~5 years ago I had to work a full week, 8h a day, to fully upgrade a medium-sized website from PHP 5.2 to 5.4, and eventually gave up. Most of the time was spent trying to cope with different datetime parsing idiosyncrasies.
  - simion314 7y ago
    I am sorry you had such a bad experience, can I ask you to give me some link or details about your issues with datetime , I want to learn about the problems I do not doubt you. I had some problems with mysql updates though, new versions had different)better default behavior). we were using an ORM for the project but the initial setup and migrations were made in plain SQL and those needed to be updated. As an example in older mysql you could have a timestamp column NULL with no default value set and now we needed to fix to set a curenttime as default.

johnday 7y ago

> If you talk about function names and parameter ordering not being consistent that is not an issue for developers using the language daily It does feel like this is analogous to saying "the holes in the floor of our building aren't an issue - all the senior devs know where they are by now"