The fastest frontend framework is no frontend framework.
Unless you absolutely need strong SPA features where things HAVE to change without a reload, then just use express and a server-side templating engine and go about your day. You'll save significant amounts of time and energy and likely wind up with a more performant/smaller result in the end.
If you really need to be a SPA, then vue or svelte are going to be a smoother dev experience of you need to learn a framework from scratch. If you already are familiar with a specific framework, then that is your next best pick. I'd stay away from react if you can, I've seen far more teams get it wrong than right and I don't think it's good stewardship to use a tool that leads to higher rates of dev errors and performance degradations over one that is more difficult to screw up.
The fastest frontend framework is no frontend framework.
It's a bit paradoxical but you can actually make a framework at least a little bit faster than typical vanilla when performing DOM updates, but also significantly faster and more responsive for when you have massive amounts of updates and you start adding schedulers, sync up with animation frames, web worker bridges, etc... all the usual good stuff that if you start adding to a vanilla app, you'd end up calling a framework anyway, in the end. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The fastest frontend framework is no frontend framework.
Unless you absolutely need strong SPA features where things HAVE to change without a reload, then just use express and a server-side templating engine and go about your day. You'll save significant amounts of time and energy and likely wind up with a more performant/smaller result in the end.
If you really need to be a SPA, then vue or svelte are going to be a smoother dev experience of you need to learn a framework from scratch. If you already are familiar with a specific framework, then that is your next best pick. I'd stay away from react if you can, I've seen far more teams get it wrong than right and I don't think it's good stewardship to use a tool that leads to higher rates of dev errors and performance degradations over one that is more difficult to screw up.
It's a bit paradoxical but you can actually make a framework at least a little bit faster than typical vanilla when performing DOM updates, but also significantly faster and more responsive for when you have massive amounts of updates and you start adding schedulers, sync up with animation frames, web worker bridges, etc... all the usual good stuff that if you start adding to a vanilla app, you'd end up calling a framework anyway, in the end. :)