Welcome to /c/php! This is a community for PHP developers and enthusiasts to share and discuss anything related to PHP. From the latest updates and tutorials, to your burning questions and amazing personal projects, we welcome all contributions.
Let's foster an environment of respect, learning, and mutual growth. Whether you're an experienced PHP developer, a beginner, or just interested in learning more about PHP, we're glad to have you here!
Let's code, learn, and grow together!
Final keywords–like locks on a door–are just a suggestion. If someone wants to light a stick of dynamite and play hot potato with it, that's their own problem. As long as they aren't wasting upstream dev's time or publishing packages that depend on this to work, it's not worth getting upset about.
As long as they aren't wasting upstream dev's time or publishing packages that depend on this to work
But exactly this will happen.
Another red flag for people hired to maintain that code, I guess.
Just because one person said "final is bad", the Laravel fanboy herd is flocking to solutions like this. In my opinion, the package per se is not bad, but the unreflected, absolute statement "final is bad" is the problem.
In my opinion, the package itself is bad. It suggests by its very existence that final is bad. It tempts to use dependencies in a way that was not intended by their developers.
This. And, unlike Lombok, there is no -deUnfinalize. Sure seems like youre stuck with fixing your codebase, when this thing finally folds.
Yes the package pushes the notion "final is bad". Throw both into the trash.