With semantic versioning b/c is allowed. For example version 8.0.0 vs 7.x.x -- version 8.0.0 could include major breaking changes (since it is a major version number change). This allows a language to evolve and grow with the needs of the users. If PHP is so `rigid` that NO B/C are allowed (regardless of major version changes) then PHP is overtly rigid and I predict it will ultimately become extinct.
On Sun, Mar 3, 2019 at 3:34 AM Thomas Hruska <thru...@cubiclesoft.com> wrote: > On 3/3/2019 1:45 AM, Ryan Jentzsch wrote: > > Thanks for the explanation of b/c. I didn't know PHP is this rigid. Now I > > do... > > It has to be. Hundreds of millions of lines of code written in PHP run > on millions of servers globally every single day. The PHP devs take > their responsibilities seriously. > > If it were a smaller, less widely used language, BC changes would be > easier to make and have fewer consequences. > > -- > Thomas Hruska > CubicleSoft President > > I've got great, time saving software that you will find useful. > > http://cubiclesoft.com/ > > And once you find my software useful: > > http://cubiclesoft.com/donate/ >
