Filter
Exclude
Time range
-
Near
What excuse do have to not read books? Listen to these greats @BillGates @elonmusk READ!! READ!! and READ... @orangebook @bookclubbar @CodeBookClub @FLJSbook #booklovers #ReadingChallenge
1
1
10 Nov 2020
"by decoupling how a function recurses over data from what the function actually does" second read at same phrase and need 10 more times. THANKS @importantshock @FLJSbook #fp @javascript_fan
1
I haven't, thanks for the link I shall read this!
2
Replying to @bagwaa
Have you checked out @FLJSBook from @getify?
1
3
"code that you cannot trust is code that you do not understand" @getify in "Functional-Light JavaScript" @FLJSBook #javascript
4
1
9
17 Aug 2020
“... partial application is strictly a reduction in a function’s arity;” —@getify, #fljsbook And, generally speaking, less arity is better. Generally. Do what you gotta when you gotta, but know there are a number of ways to address and refactor function calls with high arity.
1
4
Both QIO and cofx look related and interesting. Appreciate you sharing. Not clear that Monio merely duplicates them (I think there are reasons for Monio to still exist), but I do think I should probably cite them in Monio's docs as relevant adjacent work.
2
Thanks to @ajchambeaud I found the library I was talking about: github.com/neurosnap/cofx. Same idea of the other one I found, but this uses generators as a way of making the code more "imperative/doblocky"

1
3
I did release @FLJSbook a few years back. My latest explorations in FP may or may not end up in a sequel to that book, someday.
1
15 Jul 2020
I do love making monads more approachable, but conflating terms leads to confusion. Something with map, fold, concat, etc does not necessarily mean it’s a monad. And that is what I took you as claiming.
1
2
If you followed along and you're intrigued, check out my Monio library: github.com/getify/monio And for more reading on monads: github.com/getify/Functional… (that's appendix B of my @FLJSbook, which I also encourage you to read all of!)

6
3
49
14 Jun 2020
“... we should aspire to be able to understand our code well enough that we know the test suite will pass before it runs.” — @getify, Functional-Light JavaScript leanpub.com/fljs #FLJSbook

1
2
11
As for "best practice" i.e. efficiency, using tail calls ( TCO) can help with really deep recursion but also don't forget to consider the "human efficiency" of how long it takes you to read/write the code! Sometimes iterative code is the clearer & faster choice 🙂
1
3
so my advice would be: try normal recursion first, then apply a trampoline. I would advocate PTC form except that nobody but Webkit supports, so it's not that useful yet.
1
2
for a **lot** more detail on recursion, see ch8 of my @FLJSbook: github.com/getify/Functional…

1
2
Replying to @getifyX @getify
As always, your explanations are top notch. It's time I buy @FLJSbook.
1
I have an appendix in @fljsbook about them: github.com/getify/Functional… also, my FP course on @FrontendMasters has a whole section about them.

3
19 May 2020
I have not - I'll take a look at the book, thanks
2
14 May 2020
Just finished @FLJSbook and thought it was a good introduction to Functional Programming concepts. It was a little heady at times but still a good read overall. I still don't know what a monad is.
2
3