3 ms·
>...turn ugly when you start breaking down components into smaller and smaller components. Care to elaborate? This seems opposite to how components ought to w
by tejohnso 8y ago
>...turn ugly when you start breaking down components into smaller and smaller components.
Care to elaborate?
This seems opposite to how components ought to work.
- wolco 8y agoTake a table that is broken into rows then cells, within the cell you have a media object within that you have a list with items. Each of those become separate components. Can you reuse them, yes but it would be more helpful to keep them in one component.
- crooked-v 8y agoSo keep them in one component.
- fastball 8y agoYou can keep them in one component. Nobody is making you split every single object into discrete components.
- kccqzy 8y agoThen don't split them. If you use powerful methodologies to keep track of complex state in one component, not splitting is generally easier too, although you will lose slightly on performance. No one forces you split a component into multiple ones. I've implemented entire games in just one component with logic cleanly described by a finite state machine.
- pnloyd 8y agoReading this makes me feel better I make large monolothic components. Most examples would have you believe doing so is a big no no.