Hacker News Reader

Comment by rustc | Hacker News Reader

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.

View on HN

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.

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?

I mean even basic stuff is different. You have thead and tbody in the react example but not in the hyper example. It adds number of lines differential which I guess is supposed to be impressive but when I see stuff like that it makes me think the whole comparison is worthless since it can't be trusted.

Only use 1:1 markup/features instead of adding those "modern react" examples.

You ask this every time, but never incorporate the feedback. Why even bother?

Where is the feedback?

I'm not playing this game with you, people can go look at previous posts for your software and decide themselves.

I'll just leave one great example - you keep saying that JS can't handle more than 150k records, when people explained to you that it's simply due to the syntax you've used: https://news.ycombinator.com/item?id=43546118

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.

Did you run the React code you wrote in the blog post? It has sorting, icons, filtering, typescript types.

Yes. The React example restricts to sorting and filtering only

you could also remove those pieces from the react examples

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.

Why not just include equal features to comparisons? New framework should also handle the real-world scenarios.

Reply on news.ycombinator.com