Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalWhen a child component wants to communicate to a parent or sibling component, it makes sense to dispatch custom browser events. However, DOM events require more work when using React.
React uses its own event system and cannot directly listen for native DOM events coming from a Custom Element.
When a child component wants to communicate to a parent or sibling component, it makes sense to dispatch custom browser events. However, DOM events require more work when using React.
React uses its own event system and cannot directly listen for native DOM events coming from a Custom Element.
When a child component wants to communicate to a parent or sibling component, it makes sense to dispatch custom browser events. However, DOM events require more work when using React.
React uses its own event system and cannot directly listen for native DOM events coming from a Custom Element.
These are big and difficult problems, and as the only resident FE dev it will fall on me to find solutions to them, which could halt my productivity dead in its tracks and detract from my ability to solve problems we absolutely must, like performance in managing millions of records. He argues that this is a business critical application, and using this pattern will ensure it is able to scale if, in several years' time, it begins growing exponentially and ultimately needs to be maintained by multiple teams. I am still new here, and I don't know how plausible such massive growth is, but it seems unlikely as it is not planned for and the app performs a highly specializedspecific function. I don't believe it's worth exposing ourselves to increased complexity, slower/more development time and a host of liabilities that could put us months behind schedule (when business has already pressured us about our trajectory) in exchange for abstract benefits in theoretical scaling years down the road.
These are big and difficult problems, and as the only resident FE dev it will fall on me to find solutions to them, which could halt my productivity dead in its tracks and detract from my ability to solve problems we absolutely must, like performance in managing millions of records. He argues that this is a business critical application, and using this pattern will ensure it is able to scale if, in several years' time, it begins growing exponentially and ultimately needs to maintained by multiple teams. I am still new here, and I don't know how plausible such massive growth is, as it is not planned for and the app performs a highly specialized function. I don't believe it's worth exposing ourselves to increased complexity, slower/more development time and a host of liabilities that could put us months behind schedule (when business has already pressured us about our trajectory) in exchange for abstract benefits in theoretical scaling years down the road.
These are big and difficult problems, and as the only resident FE dev it will fall on me to find solutions to them, which could halt my productivity dead in its tracks and detract from my ability to solve problems we absolutely must, like performance in managing millions of records. He argues that this is a business critical application, and using this pattern will ensure it is able to scale if, in several years' time, it begins growing exponentially and ultimately needs to be maintained by multiple teams. I am still new here, and I don't know how plausible such massive growth is, but it seems unlikely as it is not planned for and the app performs a highly specific function. I don't believe it's worth exposing ourselves to increased complexity, slower/more development time and a host of liabilities that could put us months behind schedule (when business has already pressured us about our trajectory) in exchange for abstract benefits in theoretical scaling years down the road.
