Bundle Phobia: find the cost of adding an npm package to your bundle

Re:Bundle Phobia: find the cost of adding an npm package to ... by TAForObvReasons on Monday December 18, 2017 @01:34PM (#15953994)

The flipside is that the standard library from Java / C# are huge, large enough that there's basically one complete and proper implementation.

In JS land, you have multiple different implementations with different feature sets and behaviors. Code written for V8/chrome/node may behave differently in safari/jscore or IE/edge/chakra or firefox/spidermonkey.

[ Parent | on HN ]

Re:Bundle Phobia: find the cost of adding an npm package to ... by quantummkv on Monday December 18, 2017 @01:47PM (#15954153)

This can be the case for big or difficult to implement functionality like async/await. But for smaller functions like isArray, isObject and leftpad this should not be the case.

C++ has a lot of different standards, compilers and implementations. There are differences in vc++ and gcc that can prevent compilation without flags or custom implementations. But I am sure that simple functions like printf or strcpy behave same across implementations.

Even in Java you have Oracle JVM and android's custom dalvik/ART. But the standard Java functions still work the same. Same with .net/mono.

[ Parent | on HN ]

Re:Bundle Phobia: find the cost of adding an npm package to ... by ssalazar on Monday December 18, 2017 @01:37PM (#15954022)

By flipside are you suggesting that managing multiple feature sets/behaviors across implementations is a good thing?

[ Parent | on HN ]