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

  • pivot_root@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    1 year 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.

    • AlexOP
      link
      fedilink
      arrow-up
      5
      ·
      1 year 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.

      • Rikudou_Sage@lemmings.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        That’s gonna be the quickest issue close I am even capable of. As soon as you have problem with extending a class that’s not extendable, well, sounds like a you problem.

  • dbx12
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 year 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.

    • AlexOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year 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.

      • dbx12
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

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