4 ms·
It’s because in normal localhost you have to spin up a server in another process that serves your JS. With this there’s no server serving your JS. It’s right th
by sktrdie 5y ago
It’s because in normal localhost you have to spin up a server in another process that serves your JS. With this there’s no server serving your JS. It’s right there in the browser already. That’s what they mean.
- nitsky 5y agoI understand, but it is not obvious this provides a performance benefit which outweighs the potentials slowdowns I mentioned above. I am concerned about the trend of JavaScript tools advertising how they are “blazing fast” without any benchmarks or serious technical analysis.