4 ms·

Well, it's a problem of mixing data and visual elements. In a good model of the web, html is your data, css is your styling, and javascript doesn't really exis

• vinceguidry 8y ago
  Thanks for introducing me to the concept of the scene-graph. I tried to make an argument on a React community slack that components are purely visual, that they should express the visual structure of the web page, in the context of an argument over how state and props should be used. He hated the rise of the Redux ecosystem, and I was trying to make the point that if you don't manage global state in your application sanely, you'll only end up reinventing it poorly, passing onChange across the Atlantic in the case where your save button doesn't live in the same visual space as the rest of your form. His response was to bring up the Router component to make the point that not all components are visual. UIs are complicated things, I've found that the visual model is the best encapsulation concept. Components aren't bad, but you need to first have a need to use them, because there's definitely a tradeoff, and second you need to use the right abstraction techniques. Routing components are a hack, different pages should just load different base components in the site backend. But it seems like once someone swallows the functional paradigmatic koolaid, they lose all perspective to see when the paradigm fails to produce erudite design.
  • deleted 8y ago
    [deleted]