4 ms·
> potentially even allowing functions to become small enough that they can be inlined Apparently, that's no longer the case, at least in V8[0] Parse times how
by lhorie 5y ago
> potentially even allowing functions to become small enough that they can be inlined
Apparently, that's no longer the case, at least in V8[0]
Parse times however are indeed a real concern and start to matter a lot as you go down the list of mobile hardware and their performance. This graph[1] shows parse times for a 1MB bundle of JavaScript in various devices.
[0] https://github.com/v8/v8/commit/0702ea3000df8235c8bfcf1e99a948ba38964ee3#diff-64e6fce9a2a9948942eb00c7c1cb75f2 https://github.com/v8/v8/commit/0702ea3000df8235c8bfcf1e99a9...
[1] https://miro.medium.com/max/1400/1*dnhO1M_zlmAhvtQY_7tZmA.jpeg https://miro.medium.com/max/1400/1*dnhO1M_zlmAhvtQY_7tZmA.jp...
- vvanpo 5y agoThat graph shows results for Chrome 55. According to https://v8.dev/blog/cost-of-javascript-2019 https://v8.dev/blog/cost-of-javascript-2019, parse times in Chrome have improved significantly over the years.
- lhorie 5y agoYes, but performance differences between various devices are still fairly significant, as per your own link[0], meaning we probably shouldn't disregard potential performance gains from minification in slower devices. [0] https://v8.dev/_img/cost-of-javascript-2019/reddit-js-processing-devices.svg https://v8.dev/_img/cost-of-javascript-2019/reddit-js-proces...
- wldlyinaccurate 5y agoWhoa, I had no idea they'd fixed the inlining-by-size - thanks for pointing that out!