News for hackers. Stuff that matters.
Re:CIL (.NET bytecode) to WebAssembly compiler by WorldWideWayne on Thursday September 03, 2015 @11:56AM (#10165644)
Which library? From where? Never heard of ramda, but I can tell you it's not standard.

Why should people use JS with a non-standard library when dictionaries come built into better languages?

Re:CIL (.NET bytecode) to WebAssembly compiler by lhnz on Friday September 04, 2015 @05:58AM (#10169521)
The library is ramdajs.com and it can be grabbed from npm.

I do not agree that everything should be handled with standard libraries. It's better for these things to be modular and versioned, instead of them being pulled from a big bloated standard library.

The code clearly does what was being asked in a very simple and non-broken way.

Perhaps the issue here is that non-JavaScript engineers are used to kitchensink standard libraries and avoid mixing and matching to get the best experience the ecosystem offers.

Re:CIL (.NET bytecode) to WebAssembly compiler by WorldWideWayne on Friday September 04, 2015 @11:06AM (#10170935)
You're building a straw-man there. A standard library can certainly be made to be modular and versioned. It doesn't have to be bloated for any reason whatsoever. This is Javascript - you can chop up your scripts however you want.

The problem with mixing and matching libs is that no two JS devs do it the same. Some will even re-build the same lib that has already been built by hundreds of JS devs because NIH.

Re:CIL (.NET bytecode) to WebAssembly compiler by lhnz on Tuesday September 08, 2015 @03:51PM (#10187833)
You are the one that has built a strawman.

In your universe, engineers do not talk and accidentally decide to use two libraries that do the same thing within a project.

I work with JavaScript and I rarely see this happening.