I'm no longer a fan of using any front-end libraries at all en lieu of just using standard event listeners and web components, but in their defense, by the time that you're creating or updating that many elements, most developers are backing out of the framework anyway.
It's the primary reason virtual table libraries exist.
> I'm no longer a fan of using any front-end libraries at all en lieu of just using standard event listeners and web components
You can get away without using frontend frameworks for small and simple projects. However, for large and complex projects you will struggle. For example, try building Google Docs without a frontend library. You will struggle even if you have an army of developers at your disposal. In fact, with a larger team, a library/framework helps standardize things.
I don't know about others, but VSCode uses other libraries and tools to build on top of. It uses Electron, Monaco editor, Web components etc. It is not pure javascript/typescript.
We build large apps at my company without this and it reduces our dependency management overhead.
Most software doesn't require large teams, ones with large enough structure to utilize cross-functional teams are siloed enough that it also still doesn't matter and the most standardization that's effectively useful is the company's specific UI library for their corporate branding.
At that point you're really using the company's library, and less of the underlying framework anyway. Uber, AAA, American Express, etc. All of them do basically this.
It's the primary reason virtual table libraries exist.