4 ms·

> 1. You get what you want: a web bundler and a dev server No I just want to build an app fast. Frameworks allows this to. One NPX command gets you a running a

> 1. You get what you want: a web bundler and a dev server No I just want to build an app fast. Frameworks allows this to. One NPX command gets you a running app. > 2. No premature bargains or decisions, all this base belongs to you. Cool now you're the only snowflake in the world with a setup like your custom setup. All online help on frameworks people commonly use is useless to you, good luck > 3. Expand infinitely and meaningfully with modules you will want to utilize for covering your app's use-case, starting with react and react-dom Nope, with this naive approach you will soon encounter scalability problems, you will need code splitting, (per page maybe?), and you will inevitably re invent NextJS or a similar framework. > 1. Have to learn about your problems and discover solutions I want to focus on my client's problems not my problems > 2. Have to scroll through solutions documentation and configure them manually Yep > 3. Have to own your technical decisions and structure There is enough to own in this world. I guess you're also the kind of person who want to build your own Linux Distro and own the entire stack?

gloosx 4y ago
My npx command gives you the runnable app too, the problem with your approach is just that it is superficial, and it doesn't show a lot of comprehensions. I don't have any problem with that, since that places you behind in the competition. I see why you would want to use Next.js in order not to build it yourself, but in the first place, I don't see why you need Next.js features for a plain React app at all, and what benefits it gives, I don't see why you need to be renting a whole VPS for hosting that. React projects are typically statically built single-page apps which are not required to be statically rendered or dynamically served, you can serve the static bundle itself on a file-hosting, so the title of an OP post is just misleading, it clearly says "How to choose a framework for your React Project in 2023"

gloosx 4y ago

My npx command gives you the runnable app too, the problem with your approach is just that it is superficial, and it doesn't show a lot of comprehensions. I don't have any problem with that, since that places you behind in the competition. I see why you would want to use Next.js in order not to build it yourself, but in the first place, I don't see why you need Next.js features for a plain React app at all, and what benefits it gives, I don't see why you need to be renting a whole VPS for hosting that. React projects are typically statically built single-page apps which are not required to be statically rendered or dynamically served, you can serve the static bundle itself on a file-hosting, so the title of an OP post is just misleading, it clearly says "How to choose a framework for your React Project in 2023"