Today, it is impossible to imagine a modern large project without using Next.js or Nuxt.js.
But, nevertheless, if the task is to quickly create su...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the article!
I'd argue the opposite. I wouldn't choose a framework for a large project. They are mostly opinionated and limiting when it comes to edge cases (which often happen with larger projects).
Next.js is used by Spotify and ChatGPT. I'd like to believe there are home-grown solutions, but that's basically it.
This is pretty much like having your home bakery or run your own small dairy farm. It is not THAT hard and the result would easilly be more tasty (and healthy) than mass produced groceries from store. But it is REALLY worth your time and effort?
I rather think what to build with existing tools than creating new homemade solutions with limited usage.
But it is up to everyone's preference of course.
Yes, no one is discouraging you from using Next.js, it's just an alternative, as some solutions are not suitable for some business cases.
Nice, this reminds me how much setup is really optional. Im always tempted to just grab a framework, but sometimes its fun to build the pieces yourself. you ever find it worth skipping the big tools or does it just end up messy after a while?
honestly the whole fast-build vibe here kinda fits how i do things when i wanna skip extra setup, feels good to see this broken down so simple
his explanation is very good.
Yes
Thank you! Of course it was possible, yes.
Thanks so much for sharing this tutorial! I love the creative approach and that you're questioning the status quo (we use Go + vanilla JS so also don't subscribe to the NextJS dogma)
I would say though, that while this approach works great for prototyping, there are some performance implications worth considering for production use:
The current setup makes 5+ sequential HTTP requests on page load (one per component), which can significantly impact loading performance. You might want to consider batching these into a single API call or using HTTP/2 server push.
Since the page starts empty and populates via JavaScript, users will see a blank page initially. This affects Core Web Vitals metrics like First Contentful Paint (FCP) and Cumulative Layout Shift (CLS).
I know you mentioned this at the end about the robots.txt file, but search engines may not index the content properly since it's loaded dynamically after the initial HTML.
I can see it would be useful for internal tools where SEO isn't a concern or quick prototyping
Again, I love the thinking outside the box - thanks for sharing the approach :) I'd love to see a follow-up post exploring some of the performance concerns mentioned above.
What is Next.js & Nuxt.js, and why we can't build modern large projects without them??
Frameworks
Okay, so why we cant build modern websites without them?
We can, it just takes a long time.
It was possible to take not only the landing page, but it is simply the main page on any site, so it was taken.