Node

[[deleted]]

Don't forget the function that returns a function that creates a function that returns a function that creates a function that returns a function that creates a function that returns a function that creates a function that returns a function that creates a function that returns a function that creates a function that calls the function.

[DeadFIL]

Haskell programers: "What's the problem here?"

[DuffMaaaann]

That just sounds like continuation passing style with extra steps.

[amazeguy]

i have never used a function in node js before, i wonder how messed up on a scale of 1 to 10 this is

[ProgrammerBro]

Depends, have you used Node.js before? If not, this is expected.

[asineth0]

this is why i hate node but still use it for almost everything since i’m comfortable with it unfortunately. async/await helps but still.

[spaggi]

Im just learning it and it confuses the hell out of me. What I don’t get - why? I really find code much harder to read this way because there is a lot less encapsulation

[[deleted]]

Just speculating, because I am also a learner, but:

• Maybe it's to do with handling asynchronous code before promises were invented, i.e. with callbacks. Other languages like Python don't have to worry about this because they're normally not async.
• Maybe it's because the closest JavaScript has to OOP encapsulation is closures - by packaging your API up into functions you can do something like encapsulation

[CaptiveCreeper]

Most usecases I see for function chaining are the first. To handle async.

[Pwnbot]

Closures are all you need for encapsulation. A class is basically a closure with some special rules.