You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the job of the Memory Inspector is rendering large lists of fairly uniform character. React isn't necessarily well suited to that task. We might achieve better performance and flexibility in managing our render cycles with a different DOM management strategy.
Additional information
The text was updated successfully, but these errors were encountered:
I think we can continue to use vscode-ui-toolkit even if we don't use React. It's actually twisting React a bit to integrate its own custom HTML elements, which are the core implementation of the VSCode-like UI elements, and I think we can also access those directly or through another wrapper.
Description
Most of the job of the Memory Inspector is rendering large lists of fairly uniform character. React isn't necessarily well suited to that task. We might achieve better performance and flexibility in managing our render cycles with a different DOM management strategy.
Additional information
The text was updated successfully, but these errors were encountered: