Why heavily data-driven components , we choosing Reactjs . What different in here
Answered
I'm Han posted this in #help-forum
I'm HanOP
I read this piece on a blog when choosing technology for a trading website: "For example, if you are building a static site or an application that doesn't require complex routing, Next.js can be a good choice because it automates many of the build processes and offers built-in support for server-side rendering.
I read this piece on a blog when choosing technology for a trading website: "For example, if you are building a static site or an application that doesn't require complex routing, Next.js can be a good choice because it automates many of the build processes and offers built-in support for server-side rendering.
On the other hand, if you are working on a large-scale project that requires dynamic routing and heavily data-driven components, React may be a better option.". Is this true
I read this piece on a blog when choosing technology for a trading website: "For example, if you are building a static site or an application that doesn't require complex routing, Next.js can be a good choice because it automates many of the build processes and offers built-in support for server-side rendering.
On the other hand, if you are working on a large-scale project that requires dynamic routing and heavily data-driven components, React may be a better option.". Is this true
Answered by tafutada777
that blog is not an apples-to-apples comparison. i was a bit curious about
data-driven but it is not mentioned what it is. you might want to ignore this types of articles.14 Replies
can you please share the said blog?
Bruh there isnt anything like Next Vs React. Next IS react. It just builts on top of it to give some features and QoL improvements that React doesn't out of the box(because react isnt a framework)
You can do the exact same thing in next as you do in react, but it might not be the wisest choice.
@Clown Bruh there isnt anything like Next Vs React. Next IS react. It just builts on top of it to give some features and QoL improvements that React doesn't out of the box(because react isnt a framework)
I'm HanOP
alright, I understand there isn't a significant difference here, just a bit of confusion when they mention that being heavily data-driven would be a better choice, but they don't specify why.
that blog is not an apples-to-apples comparison. i was a bit curious about
data-driven but it is not mentioned what it is. you might want to ignore this types of articles.Answer
@I'm Han alright, I understand there isn't a significant difference here, just a bit of confusion when they mention that being heavily data-driven would be a better choice, but they don't specify why.
I think the idea is more server rendering vs client rendering
Next.js brings a whole bunch of features that are heavily targeting content websites that benefit from server-side rendering : blogs, e-commerce, think sites that have many pages
but some application do not really need those features much, for instance software-like appllications that have few pages, but are extremely interactive
think an administration dashboard
for them, you might use (more) client-side React code and data fetching. However you still need a server to run your application, tools for bundling your code etc. so you can still use Next for that
you may just use a subset of Next.js features but that's ok, and you can also use other tools such as Vite, CRA...
I'm HanOP
@Eric Burel @tafutada777 Thank you both, the answers are very detailed. I won't need to worry about this article. It doesn't contain much in-depth research here