Hacker News Reader

Comment by zarzavat | Hacker News Reader

There should be a name for the fallacy: "You don't need React to do <simple thing> therefore you don't need React".

Let's just call it "the React fallacy" because everybody always picks on React.

It's like judging a programming language based on the length of its Hello World program.

The reason I use React for simple things is because I also use React for complex things which require it (or another framework of equivalent power), and I don't want to use multiple frameworks.

After all, simple things have a habit of becoming more complex as you learn more about the requirements, but rarely the reverse. It makes sense to aim your most powerful tools at even simple problems, if it avoids a rewrite in the future.

View on HN

Pray tell, what is it that only react can do that makes you "require" it?

Easily find people to hire that know the framework and a huge ecosystem of pre-made components and utilities. No other UI framework comes close.

> The reason I use React for simple things is because I also use React for complex things which require it...

The reason I drive my 18-wheeled semi truck to the local store is because I also drive my 18-wheeled semi truck when hauling cargo across the country, and I don't want to use multiple vehicles.

Fallacies can exist in both directions. "Use the right tool for the job" is good advice.

Seems like your example isn't equivalent to op's because using multiple frameworks increases complexity while picking a different car to drive to local store doesn't.

Using multiple vehicles also increase maintenance. It totally makes sense to use the right tool. You might not want to learn how to use a screw driver instead of a hammer but both have their use.

Your comparison doesn't make any sense because React is just fine for small apps. You're yelling at someone over using their car instead of roller skates to get groceries.

His exemple makes sense... Loading 100kb for a simple page that should/could be static is not fine.

React isn't 100kb when compressed (which is how 99% of websites deliver it to clients). IIRC it's 7.4kb when minified and 2.4k when minified+gzipped. That's smaller than typically "small" frameworks like htmx.

In fact, Backbone is 17.7kb minified+g zipped. So I guess other frameworks make less sense than react?

Contrary to those woo are downvoting you, I'll say that what's wrong with your analogy is that react would be like driving the 18 wheeler across the country with the handbrake on. There's better ways to do anything.

Reply on news.ycombinator.com