Remove "final" keywords from classes and methods in vendor packages with Unfinalize

TheCee, 8 months ago

Another red flag for people hired to maintain that code, I guess.

dbx12, 8 months ago

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.

alx, 8 months ago

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.

TheCee, 8 months ago

This. And, unlike Lombok, there is no -deUnfinalize. Sure seems like youre stuck with fixing your codebase, when this thing finally folds.

dbx12, 7 months ago

Yes the package pushes the notion “final is bad”. Throw both into the trash.

pivot_root, 8 months ago

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.

alx, 8 months ago

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.