3 ms·
> I also like my components to be tightly coupled. It makes project not maintainable. So using plain JS is not an option for the large long term projects.
by vladimir-y 10y ago
> I also like my components to be tightly coupled.
It makes project not maintainable. So using plain JS is not an option for the large long term projects.
- hesarenu 10y agoI am working on a multiple large reactjs project for more then a year. You need to think in terms of components.
- vladimir-y 10y ago> You need to think in terms of components. reply Why do you think I need to think in terms of components? I'd say you need to see a bigger picture not limiting yourself by only components approach. Components/modules is an essential thing of any complex project in general, ie not specifically related to the web development, but that's not enough. Try to realize that for example using praised by hipsters mixins for inheritance makes it very complicated to track down from where things came into the final object.
- hesarenu 10y agoThink in terms of components. Design small components which would be used by larger components. As I said I am already using the approach. If you could not then maybe you need a better architecture. Components are just one part. State management is another.