Recently I tried to use Next.js for the first time...
At the beginning honestly I felt it is too much configuration. In React we already have folders, but here pages and routes come from folder structure itself. That was confusing for me first.
Slowly I started learning more about how Next.js actually works. I understood that it is not just React, but kind of improved way to write React code for frontend. Routing becomes very easy because it is already provided by the framework. No extra setup, just follow the structure.
Then I started exploring backend in Next.js and that part impressed me a lot. Before this, I mostly explored traditional Node.js backend where backend is centralized and server runs continuously. But in Next.js backend, it is different. It uses serverless routes and edge servers. Initially my head was stuck because middleware is written in different way, database connection looks little different, and nothing feels like normal Express setup.
But slowly slowly I understood the idea. These backend functions run on server when needed and then stop. It is not like a continuously running server. That mindset change was big for me as a learner.
I also realized that I don’t have to manually create routes like React or Express. Everything is handled by file structure. That is powerful but also restrictive. Because Next.js is a framework, it has rules. In Express backend I feel more flexible because I can change many things the way I want.
Still, as a new learner, my experience with Next.js is really good. I learned many new concepts, especially how frontend and backend can work together in a different way. This learning journey is helping me think differently about how web applications are built.
Still learning, still exploring.

For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)