Transducers.js Round 2 with Benchmarks

[bhouston]

In https://Clara.io we identified that _.each() and other types of function-based helpers were incredibly slow (even lodash was slow) and we had to replace these constructs in performance critical areas with raw for-loops. Three.JS we also did this.

[cdsanchez]

I'd be really interested in knowing how it compares against lazy.js: http://danieltao.com/lazy.js/

[ricardobeat]

My thoughts.

edit: added lazy.js to the benchmark and transducers.js wins hands down. Lazy also starts way behind _/lodash and only catches up after >50k elements.

[est]

previous discussion

https://news.ycombinator.com/item?id=8439547

transducers in Python

https://news.ycombinator.com/item?id=8444894

[Touche]

What problem does this solve? It seems to trade more-verbose code for being more performant in large datasets. That seems reasonable. But otherwise, in day-to-day code why would I use this?

[juliangamble]

This is an example usage based on Dr Seuss: "Green Eggs and Transducers" via @gigasquid

http://gigasquidsoftware.com/blog/2014/09/06/green-eggs-and-...

(note this is in Clojure not JavaScript - but the ideas and usages are the same).

[Thomasdah]

The goal is to be less-verbose. You are able to use tansducer-based functions (map, filter, ...) on any datastructure that is iterable. For me, performance is a bonus.

I do not know how this compares to a monad/monoid. If anyone can explain, please go ahead. Thx!

[coldtea]

Because lots of day-to-day uses large datasets? Especially since 10,000 item array is considered "large" from that perspective.

[thesorrow]

How does this compare to Bacon.js or higland ?

[kbeaty]

In regards to Bacon.js, tel had a very interesting response discussing transducers in relation to FRP/Reactive Programming in another thread [1].

[1]: https://news.ycombinator.com/item?id=8447046

[jamesrom]

Time should be on the x-axis. Independent variables on the x-axis and dependent variables on the y.

EDIT: To clarify, plotting 'seconds' over 'items per second' is needlessly confusing.

[dancole]

>> Independent variables on the x-axis and dependent variables on the y.

Correct. The independent variable being the number of items and the dependent variable being the time it takes to run said number of items.

>> Time should be on the x-axis.

Time should be on the y-axis. It's the time it takes to execute, given a set of items.

[nmjohn]

> Time should be on the x-axis. Independent variables on the x-axis and dependent variables on the y.

The graph is correct - the independent variables in this case are the number of items in the array (the x axis) and the library being tested (each line).

The dependent variable in this case is time - which is why it is on the y axis.

[mattdeboard]

I think you're just confused. From the post:

> The graph below shows the time it took to run versus the size of [the array]