3 ms·
at work we use React, though i tend to work on lower-level JS code and don't have to touch it very often. my OSS code (almost 100% libs) is vanilla JS with zer
by leeoniya 4y ago
at work we use React, though i tend to work on lower-level JS code and don't have to touch it very often.
my OSS code (almost 100% libs) is vanilla JS with zero deps.
for my own projects i've been moving to fine-grained reactivity libs, like Solid or Voby: https://krausest.github.io/js-framework-benchmark/current.html https://krausest.github.io/js-framework-benchmark/current.ht.... the numbers here are a bit misleading since the benchmark is dominated mostly by DOM layout/rendering, so a difference of even 10% is actually quite significant because it's typically pure JS / GC overhead.
React has many benefits for large, diverse teams (e.g. ecosystem, hiring, docs/google-able answers), but performance is not one of them; it has many performance footguns and landmines, especially with hooks.