Comment by spoonfeeder006
Comment by spoonfeeder006 6 months ago
Isn't using React with a static site generator framework basically the same thing but better?
Comment by spoonfeeder006 6 months ago
Isn't using React with a static site generator framework basically the same thing but better?
In theory yes, in practice good luck maintaining that if you are just a solo blogger.
I doubt your blog would last a single month without some breaking change of some sort in one of the packages.
you mean npm packages? why would you need to update those anyhow?
Because at some point it will cease to work? It needs upgrades like any other project.
Every upgrade in the JS world is very painful.
Why will they stop working eventually? Assuming they are all self contained and you don't upgrade even node js for that project
Edit: Oh right, OS upgrades could do it. Or network keys changing etc...
Yeah I guess React + SSG isn't the best choice. Nano JSX might be better
It isn't crazy, judging by the number of times I've seen posts here and on other blogs talking about a 100k web page ballooning to 8Mb because of all the Javascript needed to "collect page analytics" or do user tracking when ads are included. Granted that may not be needed for personal websites, but for almost anything that has to be monetized you're going to get stuck with JS cancer because some sphincter in a suit needs for "number to go up".
> I've seen posts here and on other blogs talking about a 100k web page ballooning to 8Mb because of all the Javascript needed to "collect page analytics" or do user tracking when ads are included
Perfect example. HN will see a page with 6Mb of images/video, 1Mb of CSS and 200Kb of JavaScript and say "look at how much the JavaScript is bloating that page".
I don't even know where to begin with the pretence that you can compare HTML with JS and somehow conclude that one is 'better' than the other. They are totally different things. JS is for functionality, and if you're using it to serve static content, you're not using it as designed.
Least unpleasant to the developer. Most unpleasant to the user. It breaks all kinds of useful browser features (which frontend devs then recreate from scratch in JS, poorly; that's probably the most widespread variant of Greenspun's tenth rule in practice).
Not remotely! Unless you meant Preact. React ships an entire rendering engine to the front-end. Most sites that use React won't load anything if javascript isn't enabled