> That was exactly my point. We are currently seeing the whole thing looping. If Gatsby is exactly the format you like, what's the problem? The fact that it us

> That was exactly my point. We are currently seeing the whole thing looping. If Gatsby is exactly the format you like, what's the problem? The fact that it uses React as a dependency? Because... it uses 'npm', the worst package manager of all history? > But let's face it, for most of the websites, you don't need those tools. I'm pretty sure asking this is against the guidelines, but I just can't resist - have you ever worked with jQuery/vanilla JS and React? If you ever, ever worked with them, one can easily see that the component model React provides gives a great productivity boost. For example, consider this[0] code from the old version of this blog: it defines a 'Code' component that allows live previews of JS code. It would be super tedious to do that every time you embed a JS example in your post. > It's even worst most of the time regarding browser performances, accessibility , SEO, navigation. No, it isn't. Gatsby is a 'static site generator', with most of the advantages and disadvantages that they provide. Navigation is faster, not slower if you've turned on JS (due to progressive enhancement) and accessibility has nothing to do with React - it's the matter of proper markup (which React can do pretty well). [0] https://github.com/joshwcomeau/blog/blob/master/src/components/Code/Code.js#L29 https://github.com/joshwcomeau/blog/blob/master/src/componen...