hugoferreira's avatar

hugoferreira liked a comment+100 XP

3mos ago

@hugoferreira You could see this was the direction when Laravel did Volt - personally I also just hate seeing it all in one file. I can understand it for really basic tiny components, and maybe I'm using LW wrong, but I reach for LW for front end interactivity & therefore the classes are never tiny enough that it doesn't just look fugly all being in one.

Also a big fan, flux sub, modal pro (from philo) and have previously donated - so not slagging, but yes I also really hope we will not be forced down this single file direction.

I like the MFC co-location approach but funnily enough would probably prefer I could make a default mfc option that just did php class and view file, without js, as my raw JS is usually tiny (I suck at FE, hence opting for LW instead of vue or something) and doesn't need its own file. Maybe this is all covered in future episodes...

hugoferreira's avatar

hugoferreira liked a comment+100 XP

3mos ago

@hugoferreira Thanks for the support! This is one of those tricky things as a creator. I want to make everyone happy, but I have to do what I think is best, otherwise, the project will get stale and I won't want to use it myself.

Livewire has actually never been MVC in the sense that there are no controllers. It's just a single component with a single view and multiple actions. If when you say MVC, you mean: separate file for php and separate file for Blade, the new multi-file components offer that.

I'm sure I don't fully understand your situation, but like you said, we are still supporting class-based for cases like yours or when people simply prefer it.

Cheers!

hugoferreira's avatar

hugoferreira wrote a comment+100 XP

3mos ago

Hi Caleb, Big fan of your work and supporter.

Used to support on Github, bought for the company where I work Flux to be included in all projects and using Livewire since v1.

A bit worried with the move from MVC strucutre to have it on the same file or in same directory but on view folder. I get the convenience of it, really get it, but it is also a problem if you use template based projects, where for a new website template you need to move code from one place to the other, just as example.

I see that you were really careful to present this new feature with the safeguards of back compability, really appreciate that, but I have to confess I'm a bit worried with the direction this is taking and that in the future, the class mode will be deprecated.

Not saying that is not cool, but we are working backwards to bring the code to html again... one of main criticism on PHP since it started and we took years to convince the enterprise clients that now is a stable language with standards, like preciselly MVC... :)

All remaining Livewire V4 features, amazing. Very nice work.

Thanks for all your dedication.