Funnily enough, I assumed folio-like routing is how it worked from the start... the web.php file totally confused me the first time I tinkered around with Laravel. Thanks for the content!
Thank you Jeffrey for sharing this new Feature for Laravel. I got a question: I understood to make it work, it´s necessary to build the folder Pages, I was wondering how it would work if I want to build Livewire 3 Full page Components (including the use of wire:navigate) I will appreciate any suggestion or comment. Greetings
ppl already moaning in the comment section. this is freaking optional stuff for a very particular setup and needs. if you don't install it, it wont be there. it's not being forced upon you. what's the point of all the hate?
Actually I remember php frameworks were back in the day But I do prefer logic not to be in the templating engine, except maybe for some template specific formating methods......maybe
We have the exact opposite of thinking. Because when i saw this, i immediately thought that oh so this is how PHP or Laravel keeps up with the game. They make their own representations of the modern ways. No wonder PHP is still alive.
It's actually similar to how you would have done things before frameworks. Your folders were basically your routing. Except back then it all lived in the public folder. That's why so many JS only devs were complaining about SSR looking like the old PHP and plain HTML ways😅
usually i dont mind automation (and some level of slowdown with that - which can be compensated by some clever caching) but this here felt only okay up to the point of mixing concerns AND introducing a separate routing (foilo’s route file) if its for a basic static page or unauthorised wordpress like function… well yeah… good. but when it tries to step out of that and moves business logic and whatnot into the view file… thats a wrong idea. and with the new route file? yay… another layer of complexity whrn you need to debug something its cool that you can just pull data out from the db without much interaction between YOUR code and the system below… but don’t mix stuff… why not add a nice liettle sql in there and just merge even the model into the view… and then just like that… you travelled back in time to 2003 and its PHP3 again :) but i see that frontend frameworks do a lot of these things … when they disguise the the thing by making every fronted element an “object” and therefore mixing the rendering with the data and controller functions. because you need to dynamically parse an H1 object into an html tag to always show the same text :) welcome to Nuxravel powered by the SCC (Spaghetti Code Convention) :)
Whatever happened to separation of concerns and all that MVC, lol. Laravel is starting to turn into a wordpress of some sort and losing focus. The laravel team probably is doing these dumb stretches to gather all kinds of users.
Beg to differ. Seems more to be inspired by the stuff next.js does. Not really that WordPress-like. And of course, very optional, so nothing forced on anyone.
![[LIVE] : ONE ลุมพินี 89 | คู่เอก "ยอดไอคิว vs คิริลล์"](http://i.ytimg.com/vi/Z3vYkHJ_5Ig/mqdefault.jpg)
You are just my programming hero, Jeff 😊
Great video! It reminds me of Nuxt routes
I think currently route approach is best way and more flexible
Funnily enough, I assumed folio-like routing is how it worked from the start... the web.php file totally confused me the first time I tinkered around with Laravel. Thanks for the content!
Nice! Thank you for covering this, Jeffrey. 😊
Great video as always! thanks Jeffrey 👍
Thank you Jeffrey for sharing this new Feature for Laravel.
I got a question:
I understood to make it work, it´s necessary to build the folder Pages, I was wondering how it would work if I want to build Livewire 3 Full page Components (including the use of wire:navigate)
I will appreciate any suggestion or comment.
Greetings
What Jeff uses for browsing? I would love to use this spotlight for navigating...
It's for svelte, nextjs, and nuxtjs user that's been forced to use Laravel for the company project. I don't hate it.
Next js based laravel folio
basically folio make laravel to nextjs ?
Looks cool, but how can we have routes that might return JSON response?
NextJS, is that you?
great video jeff! i just don't like the way folio is doing it's routing.
ppl already moaning in the comment section. this is freaking optional stuff for a very particular setup and needs. if you don't install it, it wont be there. it's not being forced upon you. what's the point of all the hate?
Remember when functional react was optional? A lot of these features start as optional but end up becoming the norm
I really don't like the notion of embracing JS frameworks' way of doing things as if they are doing right way.
Actually I remember php frameworks were back in the day
But I do prefer logic not to be in the templating engine, except maybe for some template specific formating methods......maybe
But for a small project like a Doc or Personal site, this is perfect
@@DougLopes yes it's.
We have the exact opposite of thinking. Because when i saw this, i immediately thought that oh so this is how PHP or Laravel keeps up with the game. They make their own representations of the modern ways. No wonder PHP is still alive.
It's actually similar to how you would have done things before frameworks. Your folders were basically your routing. Except back then it all lived in the public folder. That's why so many JS only devs were complaining about SSR looking like the old PHP and plain HTML ways😅
Jeffrey,What does the screen recording app use?
so the traditional way is MVC, what is this one called ?
So Folio basically makes Laravel to Nuxt, Next or SvelteKit xD
Laravel doesn’t need to cater to the NextJS crowd, routing is great as is…
What is the name of this cool terminal app?
I belive it's Warp
Starting to wonder what Laravel can't do...
Nuxt 3 in Laravel
What is this simplistic editor?
PHPStorm
Are you f..ng kidding me? OMG
What is this IDE?
PHPStorm the Jeffrey way and simplyfied.
Whats the need for this? Reinventing plain php, making the app handle less requests, slowing it down. Overengineered crap essentially
This is to keep Laravel in the playing field. If it won't keep up with the times, man idk.
usually i dont mind automation (and some level of slowdown with that - which can be compensated by some clever caching)
but this here felt only okay up to the point of mixing concerns AND introducing a separate routing (foilo’s route file)
if its for a basic static page or unauthorised wordpress like function… well yeah… good.
but when it tries to step out of that and moves business logic and whatnot into the view file… thats a wrong idea.
and with the new route file? yay… another layer of complexity whrn you need to debug something
its cool that you can just pull data out from the db without much interaction between YOUR code and the system below… but don’t mix stuff… why not add a nice liettle sql in there and just merge even the model into the view…
and then just like that… you travelled back in time to 2003 and its PHP3 again :)
but i see that frontend frameworks do a lot of these things … when they disguise the the thing by making every fronted element an “object” and therefore mixing the rendering with the data and controller functions.
because you need to dynamically parse an H1 object into an html tag to always show the same text :)
welcome to Nuxravel powered by the SCC (Spaghetti Code Convention) :)
Whatever happened to separation of concerns and all that MVC, lol. Laravel is starting to turn into a wordpress of some sort and losing focus. The laravel team probably is doing these dumb stretches to gather all kinds of users.
Beg to differ. Seems more to be inspired by the stuff next.js does. Not really that WordPress-like. And of course, very optional, so nothing forced on anyone.
Literally looks like the old way of folder based routing like people did in the 90s
This specially is for the JS community - the [id] thing is like you watch SvelteJS tutorial...
noice