I’m thinking of learning it

  • CHOPSTEEQ@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    13 days ago

    If you want to use PHP, and you want to be productive, there’s no other choice in my opinion. I will say, the brain behind it is quite opinionated and most of those opinions are correct. If you don’t agree with those opinions, you will probably find yourself hating it and fighting the Laravel Magic. Give in to the magic and get shit done.

    • TheDoctor [they/them]@hexbear.netOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      13 days ago

      I use PHP daily. The only thing that seem overly magical was Livewire, but I’ll probably end up using Solid for the frontend anyway.

      • CHOPSTEEQ@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        13 days ago

        I, and then every junior I’ve onboarded as well, struggled to grasp just how important the naming conventions are for everything to just work. Models and tables must be named a certain way or you’ll be scratching your head. Model policies must be named a certain way. On and on. You can override all those, of course, but it’s just another gotcha.

      • lelgenio@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        13 days ago

        Yeah, we tried using Livewire at work, wouldn’t recommend it for any usecase. Very buggy and unfinished, many times you’ll still need to fallback to JS, passing certain data types to Livewire components is just not supported.

        • TheDoctor [they/them]@hexbear.netOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 days ago

          Is it bad if my first reaction to this is “I can fix her”? Like I feel like if I could just use it as a component system and pass simple types as props it would work nicely. But I suppose That defeats the purpose anyway. It sounds like a pain to use for anything beyond basic contexts.