Speeding up Unreal Editor launch by not spawning 38000 tooltips

Re:Speeding up Unreal Editor launch by not spawning 38000 to... by jitl on Saturday September 06, 2025 @10:46AM (#45149735)

The post you’re replying to is saying they went FROM always having the component mounted (at least in the component tree if not in the DOM as display:hidden), TO only mounting the component when it needs to be open. They moved from the way you’re talking about, to creating the component/DOM nodes only when needed.

Excessive nodes - hidden or not - cost memory. On midrange Android it’s scarce and even if you’re not pushing against overall device memory limit, the system is more likely to kill your tab in the background if you’ve got a lot going on.

[ Parent | on HN ]

Re:Speeding up Unreal Editor launch by not spawning 38000 to... by adithyassekhar on Saturday September 06, 2025 @12:28PM (#45150665)

Especially when you know the user won't be opening half of those. I did'nt use a global one because the modals themselves have some complex logic inside.

[ Parent | on HN ]

Re:Speeding up Unreal Editor launch by not spawning 38000 to... by llbbdd on Saturday September 06, 2025 @01:14PM (#45151065)

"Devs use React because they how to use the web platform, here's how to do it right" and then posts a vanilla solution that doesn't solve understand or solve the problem. Tale as old as time. Bonus points if covering the edge cases in the vanilla solution and making it work for a second component would involve a tiny homegrown reimplentation of most of React anyway.

[ Parent | on HN ]