3 ms·
> 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 th
by codingdave 11mo ago
> 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.
/s
Fallacies can exist in both directions. "Use the right tool for the job" is good advice.
- alcaide-mor 11mo agoSeems 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.
- albuic 11mo agoUsing 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.
- DangitBobby 11mo agoYour 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.
- albuic 11mo agoHis exemple makes sense... Loading 100kb for a simple page that should/could be static is not fine.
- mardifoufs 11mo agoReact 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?
- nchmy 11mo agoContrary 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.