3 ms·

a similar argument is going on in c++ community - whether to value stability or performance. one thing that always struck me is that the number of developers o

a similar argument is going on in c++ community - whether to value stability or performance. one thing that always struck me is that the number of developers of X language is some factor times the number of developers at the point in time when it first had a strong community. if that factor is greater than 2, and it usually is, then to me dividing the language into two distinct dialects with different values makes sense.

paulryanrogers 6y ago
Perhaps spreading out the breaking changes as PHP has done from 4 through 7.
- dgellow 6y ago
  One thing specific to C++ is that the main point of discussion isn't necessarily about the language itself, instead it is about breaking the ABI or not moving forward. Breaking the ABI would allow for significant performance improvements, but that would require a huge amount of libraries to be recompiled, which is something a lot of vendors don't want and sometime cannot because sources aren't available anymore.
  - im3w1l 6y ago
    What about something like this? https://devblogs.microsoft.com/oldnewthing/20040108-00/?p=41163 https://devblogs.microsoft.com/oldnewthing/20040108-00/?p=41...
- AlexMax 6y ago
  As somebody who used PHP through that transition, I have to say that the 5-7 (skipping 6) transition was especially well handled from my perspective. There was certainly breakage, but the amount of things you had to fix was relatively small. https://www.php.net/manual/en/migration70.incompatible.php https://www.php.net/manual/en/migration70.incompatible.php It was really easy to write code that worked in both 5 and 7. Most of my time was spent waiting for dependencies or frameworks to make the same jump. Then again, I suppose PHP developers had the hindsight of Python 3 and Perl 6 as a gigantic warning klaxon of what not to do.

3 ms·

a similar argument is going on in c++ community - whether to value stability or performance. one thing that always struck me is that the number of developers o

by mkoubaa 6y ago

paulryanrogers 6y ago
Perhaps spreading out the breaking changes as PHP has done from 4 through 7.
- dgellow 6y ago
  One thing specific to C++ is that the main point of discussion isn't necessarily about the language itself, instead it is about breaking the ABI or not moving forward. Breaking the ABI would allow for significant performance improvements, but that would require a huge amount of libraries to be recompiled, which is something a lot of vendors don't want and sometime cannot because sources aren't available anymore.
  - im3w1l 6y ago
    What about something like this? https://devblogs.microsoft.com/oldnewthing/20040108-00/?p=41163 https://devblogs.microsoft.com/oldnewthing/20040108-00/?p=41...
- AlexMax 6y ago
  As somebody who used PHP through that transition, I have to say that the 5-7 (skipping 6) transition was especially well handled from my perspective. There was certainly breakage, but the amount of things you had to fix was relatively small. https://www.php.net/manual/en/migration70.incompatible.php https://www.php.net/manual/en/migration70.incompatible.php It was really easy to write code that worked in both 5 and 7. Most of my time was spent waiting for dependencies or frameworks to make the same jump. Then again, I suppose PHP developers had the hindsight of Python 3 and Perl 6 as a gigantic warning klaxon of what not to do.