Functional Programming using JavaScript
scott.sauyet.com
Functional Programming using JavaScript
1–10 of 88 posts
Re: Functional Programming using JavaScript
#2I assume these slides are from a talk?
Re: Functional Programming using JavaScript
#3I assume these slides are from a talk?
Correct, but not mine. I think they are quite interesting and they are well understood outside the context of the talk
Re: Functional Programming using JavaScript
#4There is also @fogus' book: http://shop.oreilly.com/product/0636920028857.do
I haven't read it yet.
Re: Functional Programming using JavaScript
#5I believe this is the author of Ramda, yes?
I can't find the talk, anybody got a link?
(Ramda is pretty bad ass.) http://ramda.github.io/ramdocs/docs/
Re: Functional Programming using JavaScript
#6There is also @fogus' book: http://shop.oreilly.com/product/0636920028857.do I haven't read it yet.
It's a fantastic book for getting your mind used to the functional way of thinking.
I'd also recommend JavaScript Allonge on the same topic. https://leanpub.com/javascript-allonge
Re: Functional Programming using JavaScript
#7This is a really nice presentation that introduces a lot of concepts well and also helps a person conceptually understand how functional programming fits in to the larger programming world.
Book mark it and share it.
Re: Functional Programming using JavaScript
#8These slides are very difficult to read on a touch device.
Re: Functional Programming using JavaScript
#9I put together a similar talk last summer: http://thedrearlight.com/functional-js-wut unfortunately, don't have the vid either, but the slides might be complementary to the ones linked by the OP.
--edit It's formatted kinda weird, where both up/down and left/right arrows navigate through the different sections.
Re: Functional Programming using JavaScript
#10finally, a slide deck that uses `history.replaceState` instead of `history.pushState`. no more having to hit "back" 90 times to exit the deck. how the latter ever became a pattern is beyond me.
[EDIT] it probably became a pattern because of browsers that didnt implement the history API, so all hashchange events were pushed onto the history stack.