|
|
|
|
|
|
by hpvic03
1975 days ago
|
|
|
Here comes the classic HN middle-brow dismissal :) TodoMVC is meant to be a minimalist demo, not a battle-hardened app. We switched from React to Reflex 7 months ago. We have fewer bugs than we did with React, and we ship things about 3 times faster. 5/5 of us strongly prefer Reflex over React. Including one of us who was a big React aficionado beforehand. Just wanted to put that out there for anyone considering Reflex, a bug in TodoMVC is not a harbinger of a bad framework. |
|
|
Personally, I enjoy React on the front-end but don't currently like any back-end framework, so Reflux may well be better in aggregate.
(FWIW, I have a PhD in computer science and big part of that was on web applications and frameworks for them, combined with ~15 years commercial experience mastering web development, so this wasn't meant to be a middle-brow dismissal. As I said, it is exciting, I'm just not convinced.
I think there is some merit in the argument that too much cleverness can be dangerous. Battle-hardened is tricky; I agree TodoMVC is meant to be a minimalist demo, but if a minimal demo can have subtle bugs caused by the cleverness of the data binding, how much more so a real app with a much more complex data model?
But I guess it does eliminate whole other classes of bug, so I can believe it works less buggy and more productive better than React+some back end.
I certainly find the current front/back split endlessly painful. I am also excited by the new React Server Components which might be another good solution to that.)
EDIT TO ADD: I guess what I was trying to say is: I found this interesting, and I looked at it, and then I found this bug in the example, and I wonder if this framework might make a bug like that more likely because the power of making some things easier is obscuring what is happening in some cases, and I don't know if that trade-off is worth it.