It's neat that the article presents Laravel as an alternative, but the audience seems to be JS / node devs here. I'm a JS dev and haven't touched PHP since around 2010 when I was at Yahoo and they started to move to node.js.
The article needs to have a better section on why move to PHP and use Laravel. There's overhead in learning both a language and a framework, and "PHP also does it" isn't a compelling enough argument for me.
That's a good point. The author should have mentioned the more robust standard library, high package quality and package stability, helpful community, and simpler/predictable hosting solutions.
That was a good read. I tend to believe that Nextjs is a tool for frontend developers who want to build a full-stack app and Laravel is a tool for backend developers that want to build a full-stack app as well.
In my opinion the perfect combination would be to use Next.js for the frontend and Laravel for the backend as an API.
3 comments
[ 1.6 ms ] story [ 20.2 ms ] threadThe article needs to have a better section on why move to PHP and use Laravel. There's overhead in learning both a language and a framework, and "PHP also does it" isn't a compelling enough argument for me.
In my opinion the perfect combination would be to use Next.js for the frontend and Laravel for the backend as an API.