I use PHP daily. The only thing that seems overly magical on a cursory glance is Livewire, but I’ll probably end up using Solid for the frontend anyway.
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.
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.
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.
I use PHP daily. The only thing that seems overly magical on a cursory glance is Livewire, but I’ll probably end up using Solid for the frontend anyway.
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.
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.
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.