3 ms·
I like it. In fact I like it more than React, which I am not using (still a happy Backbone user). A thought that I share, from the guide: "API-wise, one issue
by twsted 11y ago
I like it. In fact I like it more than React, which I am not using (still a happy Backbone user).
A thought that I share, from the guide:
"API-wise, one issue with React (or JSX) is that the render function often involves a lot of logic, and ends up looking more like a piece of program (which in fact it is) rather than a visual representation of the interface. For some developers this is a bonus, but for designer/developer hybrids like me, having a template makes it much easier to think visually about the design and CSS. JSX mixed with JavaScript logic breaks that visual model I need to map the code to the design. In contrast, Vue.js pays the cost of a lightweight data-binding DSL so that we have a visually scannable template and with logic encapsulated into directives and filters."
What do you think?
- seivan 11y agoMassive render() sounds like those massive viewControllers from Cocoa. With experience it slowly goes away. But yeah it can be daunting to look at sample codes and see 300 lines of render(). It helps if it's broken down in named function calls, but still makes you jump around.
- k__ 11y agoYou can always decompose the components, if your render() gets to big.
- xixixao 11y agoIt is a trade off. It is easy to implement any logic with React. Simple databinding works well until you need that logic.
- Offler 11y agoIt sounds like the sort of mistake newbie React developers make, you quickly learn to decompose your render into smaller components.