3 ms·

> I haven't had a use for this yet, but I'm always amazed by how PHP manages to move forward without breaking BC. This. If I were a Python developer (of the l

by AlexMax 12y ago

> I haven't had a use for this yet, but I'm always amazed by how PHP manages to move forward without breaking BC. This. If I were a Python developer (of the language itself), I would be paying very close attention to how PHP has handled deprecation and breaking changes.

TazeTSchnitzel 12y ago
There's been an effort with PHP 7 to try and avoid a Python 2/3-style situation. The PHP 5 to 7 jump should be much smaller than from 4 to 5.
- Danack 12y ago
  >The PHP 5 to 7 jump should be much smaller than from 4 to 5. And also the jump from 5.4+ to 7 is probably smaller than the jump from 5.2 to 5.3. Although I think the PHP project does need to support versions for longer, the adoption rate of 7 is going to be quite rapid due to the low barrier of doing it, and the massive performance and language gains.
imakesnowflakes 12y ago
Like this? http://www.reddit.com/r/lolphp/comments/2wse9i/just_ran_into_this_one_php_backward_compatibility/ http://www.reddit.com/r/lolphp/comments/2wse9i/just_ran_into...
Latty 12y ago
Really? I see it as the exact opposite. Sure, Python added some pain from 2-3. They did so to fix the main flaws in the language and remove deprecated stuff. The language is now far better and the cost has mostly been paid. The alternative is the PHP approach where everything hangs around for ever, and everyone is using deprecated stuff, everything is named weirdly and lots of extra gunk has to be shoved in to try and make it work in a sane way because "we didn't want to break anything". I understand why some people prefer that, and why it's the way most languages go (Java does the same thing, just with way less movement in general compared to PHP), but it means that the language gets worse over time. Eventually, if you don't do that breaking change, the language will get replaced by something that doesn't need all the cludge.
ChikkaChiChi 12y ago
Python 2 -> 3 did not have the luxury that PHP did with 4 -> 5. Python still worked, whereas PHP 4 was running around with its hair on fire screaming for a fire extinguisher that was PHP 5. Bad analogy, but the point is that Python still worked for most people so the upgrade process was slow. I think Go is going to have issues similar to Python when they make the jump to 2.0. The devs are already on record saying that BC will break.

by AlexMax 12y ago

TazeTSchnitzel 12y ago

There's been an effort with PHP 7 to try and avoid a Python 2/3-style situation. The PHP 5 to 7 jump should be much smaller than from 4 to 5.

Danack 12y ago
>The PHP 5 to 7 jump should be much smaller than from 4 to 5. And also the jump from 5.4+ to 7 is probably smaller than the jump from 5.2 to 5.3. Although I think the PHP project does need to support versions for longer, the adoption rate of 7 is going to be quite rapid due to the low barrier of doing it, and the massive performance and language gains.

imakesnowflakes 12y ago

Like this? http://www.reddit.com/r/lolphp/comments/2wse9i/just_ran_into_this_one_php_backward_compatibility/ http://www.reddit.com/r/lolphp/comments/2wse9i/just_ran_into...

Latty 12y ago

Really? I see it as the exact opposite. Sure, Python added some pain from 2-3. They did so to fix the main flaws in the language and remove deprecated stuff. The language is now far better and the cost has mostly been paid. The alternative is the PHP approach where everything hangs around for ever, and everyone is using deprecated stuff, everything is named weirdly and lots of extra gunk has to be shoved in to try and make it work in a sane way because "we didn't want to break anything". I understand why some people prefer that, and why it's the way most languages go (Java does the same thing, just with way less movement in general compared to PHP), but it means that the language gets worse over time. Eventually, if you don't do that breaking change, the language will get replaced by something that doesn't need all the cludge.

ChikkaChiChi 12y ago

Python 2 -> 3 did not have the luxury that PHP did with 4 -> 5. Python still worked, whereas PHP 4 was running around with its hair on fire screaming for a fire extinguisher that was PHP 5. Bad analogy, but the point is that Python still worked for most people so the upgrade process was slow. I think Go is going to have issues similar to Python when they make the jump to 2.0. The devs are already on record saying that BC will break.