I made the current system with convoluted hooks and stuff to support both reactive and active applets. With hooks, a parent applet updates only when needed, so if its children are reactive, then the parent is reactive and if the children are active, then the parent is active.
I previously thought that avoiding multi-process as much as possible was best for performance because I thought IPC would be really tricky. I would only do multi-process when interfacing with wayland apps.
I still think that for reactive applets, keeping it in one thread is pretty optimal. But for active applets, multi-process might be better than simple multi-threading. In principal, it is better for isolation, but I mean that even for efficiency, multi-process might be better. Further research should be done on the efficiency.
If multi-process does offer better performance, I might force active applets to be multi-process.
I made the current system with convoluted hooks and stuff to support both reactive and active applets. With hooks, a parent applet updates only when needed, so if its children are reactive, then the parent is reactive and if the children are active, then the parent is active.
I previously thought that avoiding multi-process as much as possible was best for performance because I thought IPC would be really tricky. I would only do multi-process when interfacing with wayland apps.
I still think that for reactive applets, keeping it in one thread is pretty optimal. But for active applets, multi-process might be better than simple multi-threading. In principal, it is better for isolation, but I mean that even for efficiency, multi-process might be better. Further research should be done on the efficiency.
If multi-process does offer better performance, I might force active applets to be multi-process.