this post was submitted on 10 Oct 2023
15 points (100.0% liked)

PHP

544 readers
93 users here now

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!

founded 1 year ago
MODERATORS
 

For me personally this feels very wrong. What do you think about that?

you are viewing a single comment's thread
view the rest of the comments
[–] dbx12@programming.dev 2 points 1 year ago (3 children)

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@programming.dev 1 points 1 year ago (2 children)

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@programming.dev 2 points 1 year ago* (last edited 1 year ago)

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

[–] dbx12@programming.dev 1 points 1 year ago

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