3 ms·
For most applications on most consumer devices, benchmarks comparing the time it takes to update thousands of rows are not really relevant, other considerations
by andai 5y ago
For most applications on most consumer devices, benchmarks comparing the time it takes to update thousands of rows are not really relevant, other considerations will have a stronger impact.
However, the lighter frameworks (where most of the work is done at compile-time and the result is highly optimized vanilla JS) really shine in specialized usecases like underpowered embedded devices, where the more popular frameworks introduce too much latency (>0.5s) for a smooth user experience.[0]
[0] - https://twitter.com/sveltejs/status/1088500539640418304 https://twitter.com/sveltejs/status/1088500539640418304
(That being said, it is kind of hilarious to me the world we live in where we're running an entire web browser on an embedded device just so we can use JavaScript to program it.)