Comment by tipiirai
7 days ago
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.
Did you run the React code you wrote in the blog post? It has sorting, icons, filtering, typescript types.
1 reply →
you could also remove those pieces from the react examples
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?
You ask this every time, but never incorporate the feedback. Why even bother?
2 replies →
Only use 1:1 markup/features instead of adding those "modern react" examples.
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.
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.