Optimizing Reusable Components and Addressing Performance Issues in Weweb Editor
In this meeting, the State Changers discuss a challenge with reusing a heavy component in multiple parts of an application. The component is causing crashes in the editor and making development time longer. They mention that Weweb is planning to introduce reusable components in the future, but it's unclear when that will happen. One possible solution discussed is turning the component into a view component or building something outside of Weweb and importing it. However, this would increase the maintenance cost and ownership of code. The State Changers recommend sticking with copying the component for now and considering replacing it with the new feature when it becomes available or if it becomes a high impact issue. They also discuss the possibility of the crashes being due to limited memory in the computer and suggest upgrading to a more powerful laptop or trying alternative browsers to see if it improves performance. Overall, the State Changers provide insights on how to approach the problem and prioritize user experience and maintenance cost.