3 ms·

The author makes a few good points but on average sounds like an old man complaining about everything. There is a reason React took off, and there is a reason p

by csomar 2y ago

The author makes a few good points but on average sounds like an old man complaining about everything. There is a reason React took off, and there is a reason people choose React. Sure, if you are building a simple content heavy front-end, it doesn't make sense to chose a React framework or React at all. But many apps today come with heavy front-end interactions and have to sync with their back-end in real time. Good luck doing that with jQuery Ajax. And you can't blame the bootcampers. They were promised riches after a 6 months bootcamp. They were taught React and had little interactions with HTML. So they are doing what anyone else in their position will have done. So when they were out in the market, then React is was. Suddenly, everything became a React component; and if you made a website today, you'd better off start with React. In defense of React/NextJs: I have been blogging for 10+ years. I started by using WordPress. I have constantly failed to maintain a server up and running for more than a year. There is always something that comes up. A bad WordPress update, DB goes wrong, a failed payment, a bad WordPress plugin update, Server goes down because?, etc... 5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Not sure I'd say the same about WordPress.

lelanthran 2y ago
> There is a reason React took off, and there is a reason people choose React. Sure, there's a reason. Doesn't mean it's a good one :-/ > 5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Not sure I'd say the same about WordPress. Is 5 years considered a long time? Is that the bar? Because >6 years ago I wrote an internal site/app in C# using Jquery for front-end, and that is still up, working and being used by a few thousand people daily. It's even being extended every now and then. No NPM, no React, no Vue, no Next, no front-end build step.
manuelmoreale 2y ago
I coded this one for a friend more than 6 years ago: https://designed.space https://designed.space It runs on a basic LEMP stack (or rather a LEP since it's a file based cms) on a VPS I have not touched in years. The stack is outdated, the CMS is outdated. It runs just fine with no issues. I can move it to an up to date VPS and port it to a recent version of the CMS in a couple of hours and it would then be fine for probably another 6 or 7 years.
sebazzz 2y ago
> 5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Now try actually checking out the code and building it. I’m sure there is some Node.js runtime feature that is no longer supported in the LTS version you currently have installed on your notebook.

by csomar 2y ago

lelanthran 2y ago

> There is a reason React took off, and there is a reason people choose React. Sure, there's a reason. Doesn't mean it's a good one :-/ > 5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Not sure I'd say the same about WordPress. Is 5 years considered a long time? Is that the bar? Because >6 years ago I wrote an internal site/app in C# using Jquery for front-end, and that is still up, working and being used by a few thousand people daily. It's even being extended every now and then. No NPM, no React, no Vue, no Next, no front-end build step.

manuelmoreale 2y ago

I coded this one for a friend more than 6 years ago: https://designed.space https://designed.space It runs on a basic LEMP stack (or rather a LEP since it's a file based cms) on a VPS I have not touched in years. The stack is outdated, the CMS is outdated. It runs just fine with no issues. I can move it to an up to date VPS and port it to a recent version of the CMS in a couple of hours and it would then be fine for probably another 6 or 7 years.

sebazzz 2y ago

> 5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Now try actually checking out the code and building it. I’m sure there is some Node.js runtime feature that is no longer supported in the LTS version you currently have installed on your notebook.