Comment by rustc
7 days ago
What's up with the code comparisons under "Complex components"? Why does the React version include so much more stuff than the Nue version? Does Nue automatically inject all those features in your app with just a "card" class on the top level element? The React version has full styling, icons, sortable columns, etc.
This happens every single time this framework is posted.
- The post makes some outlandish, to-good-to-be-true claims.
- It traction because A: it mentions React and B: who doesn’t sometimes wish development could be simpler.
- Readers call out the claims for being misleading or outright lies.
- The author deflects with “I could easily add that”, “you don’t need that”, or “keyed lists are unnecessary”[^1].
[^1]: https://news.ycombinator.com/item?id=37735353
That isn't necessarily deflecting if he can back it up.
That said, I would have liked an answer to your question:
https://news.ycombinator.com/item?id=37735475
...and still would.
This is a prime example of how complexity grows and how simple components remain simple. Just look for the button example: the one button being larger than the entire app. Consider going on from there. Think legos: the 2/4/8 units scale, while the more complex units struggle to fit together.
Your table does not have the same features as the React one, so this comparison does not make any sense.
What's the difference? I can easily add the missing peaces.
4 replies →
I don't love or use React but these examples are disingenuous.
It sounds like you're arguing that "React devs don't know how to manage complexity" which is a completely separate issue than React itself.
I definitely want the examples to be exact. How to fix exactly?
5 replies →
These examples are deliberately misleading. The react code does not need to look like this mess.
I want the examples to reflect real-world scenarios. Please explain how to simplify the React code. I'll fix it immediately.
1 reply →