Software Engineer @bug0
I'm Favourite Jome, a Software Engineer focused on building reliable systems, great developer tooling, and seamless user experiences.
Markdown supported Β· ββ΅ to post
You did a great job on this article. I was in almost the same position thinking why should I learn this. But I ultimately took the time to work with it and I like Next.js alot.
It is funny how paged based routing is cool again when that used to be the only option :)
I always loved the idea of having a base page and then hydrating the data in the page vs having a blank page and waiting for the data fetch to happen to be able to see something. It is how I used to work with Angular 1 back in the day. It is great to see Next.js use that paradigm.
Keep up the good work and I look forward to reading more from you.
This topic addreses my concerns about Next.js. Thanks for the article. I enjoyed reading it.
The article is simple and easy to understand, even though I use neither. At least now, I'll understand some of the jargons my brother uses and I'll be able to ask questions. Thank you also for the mention; Im happy you got around to releasing it. Looking forward to see more of your articles.
Thanks Shane π,
I had no choice but to learn Next.js for work some years ago, and it's been a fun ride ever since using the framework.
Though I haven't used Angular, learning the new paradigm Next.js brings to the table has been both stressful and insightful at the same time π
I see the benefits of the new paradigm and it is worth learning
Happy New Year, Shane. I plan on sharing more articles this year π€©
Favourite Jome
Gergo Starosta
Such a great and detailed post! Next.js is the go to for me, it is like React on steroids.