These are chat archives for ramda/ramda

6th
Oct 2015
David Chambers
@davidchambers
Oct 06 2015 04:44
I'm interested to learn what people think of ramda/ramda#1426. If the reaction is favourable, I'm excited by the thought of where this might lead.
David Chase
@davidchase
Oct 06 2015 13:13
@davidchambers :thumbsup: thats awesome!
Martin Algesten
@algesten
Oct 06 2015 13:14
davidcha...
the world is spinning.
Scott Sauyet
@CrossEye
Oct 06 2015 13:14
davidchachacha...
David Chase
@davidchase
Oct 06 2015 13:27
you guys really confused by the names?
Martin Algesten
@algesten
Oct 06 2015 13:27
just me :)
Scott Sauyet
@CrossEye
Oct 06 2015 13:29
Not yet. But when davidchalmsford and davidchapman join, I might stay to wonder.
Start to wonder.
Raine Virta
@raine
Oct 06 2015 13:41
luckily your avatars are pretty distinct
Craig Dallimore
@craigdallimore
Oct 06 2015 15:54
About to upgrade from 0.11 -> 0.17, thank you for the API change guides!
Scott Sauyet
@CrossEye
Oct 06 2015 15:57
Although others have contributed, whitefish thank @davidchambers, who's done the bulk of the work.
Craig Dallimore
@craigdallimore
Oct 06 2015 15:57
@davidchambers I am grateful.
Scott Sauyet
@CrossEye
Oct 06 2015 15:58
How does "especially" turn into "whitefish"? :smile:
One warming about 0.17: #1318, will be fixed in the next release.
Craig Dallimore
@craigdallimore
Oct 06 2015 15:59
Oh, good I didn't know what whitefish meant and I was too shy to ask
Scott Sauyet
@CrossEye
Oct 06 2015 15:59
Auto-uncorrect.
Craig Dallimore
@craigdallimore
Oct 06 2015 16:01
Dang, I use pipe and compose a lot
David Chambers
@davidchambers
Oct 06 2015 16:32
@craigdallimore, you might like to upgrade to v0.15.x then wait for v0.18.0 before upgrading further.
Francisco Ryan Tolmasky I
@tolmasky
Oct 06 2015 18:01
hey guys, I'm trying to build the docs but keep getting "Running "jsdoc:docs" (jsdoc) task No source files defined" with grunt docs (sorry used to gulp), is there another command I should be using
David Chambers
@davidchambers
Oct 06 2015 18:03
I suggest trying some of the "scripts".
Craig Dallimore
@craigdallimore
Oct 06 2015 18:03
@davidchambers noted, thanks
David Chambers
@davidchambers
Oct 06 2015 18:04
v0.18.0 will hopefully be out this week, so you shouldn't be waiting long. :)
Francisco Ryan Tolmasky I
@tolmasky
Oct 06 2015 18:05
ah cool thanks!
boxofrox
@boxofrox
Oct 06 2015 19:04
Looking forward to 0.18, @davidchambers. thanks for your work, and to all the other contributors :smile:
boxofrox
@boxofrox
Oct 06 2015 20:18
I was reading https://github.com/ramda/ramda/issues/732#issuecomment-70369101 and thinking about the possibility of creating a mirror of ramda with error checking enabled for debugging purposes. So far I've been able to figure out most errors from the stack traces I get, but at some point I figure it'll be nice to swap in an API compatible ramda-inquisitor with pessimistic assertions to check for code smells/errors and such during development. Does that sound like a reasonable approach or is there a better alternative?
Scott Sauyet
@CrossEye
Oct 06 2015 20:27
@boxofrox: we've talked about creating such several times but there had never seemed to be a real appetite. The more common response had been to continue to use Ramda as a fairly low-level library and adding in Sanctuary when looking for higher-level abstractions.
David Chambers
@davidchambers
Oct 06 2015 20:35
@boxofrox, my view is that debugging via stack traces is not an efficient, enjoyable way to write programs. I plan to get to plaid/sanctuary#75 at some point. The resulting package will provide a convenient way to wrap Ramda and other libraries. If you're interested in this possibility, chime in on the issue to push it a few pegs up my to-do list.
Denis Stoyanov
@xgrommx
Oct 06 2015 20:43
Ramda vs mori vs lodash vs etc. http://jsperf.com/plain-js-vs-immutable-vs-mori/39
boxofrox
@boxofrox
Oct 06 2015 20:48
Lies!!! @xgrommx, I was just looking at that. Might be worthwhile to add a test for mori without the .f2 et. al. to see where it's performance lands with dynamic dispatch. If it's near Ramda, then this might be one method of making Ramda more performant.
Denis Stoyanov
@xgrommx
Oct 06 2015 20:50
@boxofrox please do =) You can change it if you know right way.
boxofrox
@boxofrox
Oct 06 2015 20:58
i'll see what i can do :)
Scott Sauyet
@CrossEye
Oct 06 2015 21:01
That powerful test seems to have disappeared.
Denis Stoyanov
@xgrommx
Oct 06 2015 21:02
@CrossEye looks like yes. Somebody deleted it =(
boxofrox
@boxofrox
Oct 06 2015 21:03
It has :fire:
Frederik Krautwald
@Frikki
Oct 06 2015 21:07
What the $#!
Raine Virta
@raine
Oct 06 2015 21:08
@boxofrox you might like https://github.com/raine/treis
Denis Stoyanov
@xgrommx
Oct 06 2015 21:09
@Frikki I see :smile:
Frederik Krautwald
@Frikki
Oct 06 2015 21:24
@boxofrox @xgrommx I got a version saved from revision 2. It is not what we looked at with rev. 38, but maybe you want to fix it? http://jsperf.com/plain-js-vs-immutable-vs-mori
boxofrox
@boxofrox
Oct 06 2015 23:03
@raine sweet! that looks more sophisticated than the unary trace function i've been print-logging with.
var trace = R.curry(function (tag, x) {
  console.log(tag, x);
  return x;
});
boxofrox
@boxofrox
Oct 06 2015 23:21
@Frikki, I want to say the mori example in rev 38 was more point-free than in rev 2. The javascript sources may be suspect. I don't recall whether rev 38 used different cdn. Will see if I can add a point-free version later.
boxofrox
@boxofrox
Oct 06 2015 23:27
Then again, I may be wrong about that mori example.