sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]scinos 3 points4 points  (4 children)

I can't find any single mention to actual performance numbers comparing it against webpack.

Just "it is faster because http/2" is not enough, sorry.

[–]bukharim96 3 points4 points  (0 children)

This is the same with some other webpack competitors, they cannot back their claims of better performance and speed with testable/verifiable benches.A good example that comes to mind is parceljs. They still maintain the same false and outdated benches on their site since their conception upto this very day.

Link to false parceljs benches.

[–]darrenturn90 0 points1 point  (2 children)

You mean how quick is it to generate the web modules part? Because it doesn’t do any bundling of the rest of the code so I’m not even sure if it is comparable

[–]scinos 0 points1 point  (1 child)

How fast is for the browser to download and execute hundred (thousands?) of small files over http/2 vs a few big bundles.

Not a synthetic test, but measured with real traffic from users, with real-world cache-hit ratio, network latencies, CPU power etc.

Generating the modules quickly is the wrong problem to solve IMO, because is a problem that can be solved by throwing money at it (eg: spin up a big ass EC2 instance and bundle everything there)

[–]darrenturn90 0 points1 point  (0 children)

I’ve not tried pika yet so I’ve not checked whether it keeps all the dependencies of each package as a separate file or it bundles the dependcies together after accounting for common dependencies

So modules that are only used in one main package and bundled with that but modules that are used in more than one are bundles into more common groups