I'm a software developer who writes about Laravel, JavaScript, Rails, Linux, Docker, WordPress and the tech industry. Follow me on Twitter @tylerlwsmith
I think you may have accidentally stumbled into the point of the article. This article is about my experience. I move fast in PHP because I'm familiar with it, which is why this is titled "Reflecting on a year with Node.js and why I should have stuck with Laravel."
The article is not titled, "Reflecting on a year with Node.js and why you should use Laravel instead."
The only concrete recommendation I give is "use the fastest, most productive tool you have available to kick apps out the door quickly and get feedback from your users." For me, that tool is Laravel.
I may not have made that clear enough in my article, so thank you for flagging that. Merry Christmas!
I know this is one year old. But what Andreas is saying is not making any sense, NextJS is a front-end framework, it includes nothing that Laravel offers, also, Laravel is a back-end framework, so you comparing the two doesn't even make sense. You either don't know what NextJS is or you talk about NestJS, they are 2 different ends of the world
I'm a software developer who writes about Laravel, JavaScript, Rails, Linux, Docker, WordPress and the tech industry. Follow me on Twitter @tylerlwsmith
Funny stuff, now what i said is not really true anymore.
Since the new router in Next.js and React Server Components, next.js can really be considered a back-end framework now.
Kudos to the Next.js team for making next.js what php was able to do since day one of the release, but, with included reactivity, which i still don't know if it is good or not. The line of separation between front-end and back-end are now separated by a "use client" text at the top of the file. Weird times we live in
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Andreas,
I think you may have accidentally stumbled into the point of the article. This article is about my experience. I move fast in PHP because I'm familiar with it, which is why this is titled "Reflecting on a year with Node.js and why I should have stuck with Laravel."
The article is not titled, "Reflecting on a year with Node.js and why you should use Laravel instead."
The only concrete recommendation I give is "use the fastest, most productive tool you have available to kick apps out the door quickly and get feedback from your users." For me, that tool is Laravel.
I may not have made that clear enough in my article, so thank you for flagging that. Merry Christmas!
Andreas, please direct me to good tutorials about the JS ecosystem itself.
I know this is one year old. But what Andreas is saying is not making any sense, NextJS is a front-end framework, it includes nothing that Laravel offers, also, Laravel is a back-end framework, so you comparing the two doesn't even make sense. You either don't know what NextJS is or you talk about NestJS, they are 2 different ends of the world
Wow, it's actually been exactly one year since this was published. Thanks for giving it a read!
Funny stuff, now what i said is not really true anymore.
Since the new router in Next.js and React Server Components, next.js can really be considered a back-end framework now.
Kudos to the Next.js team for making next.js what php was able to do since day one of the release, but, with included reactivity, which i still don't know if it is good or not. The line of separation between front-end and back-end are now separated by a "use client" text at the top of the file. Weird times we live in