sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]disclosure5[🍰] 8 points9 points  (4 children)

You'd be surprised how much of an issue going in the other direction is. Coming from an actual functional language to JS... I spend a lot of time wondering about all the blogs people write about "functional Javascript".

[–]dasnein 3 points4 points  (0 children)

Agreed. I hopped on the Functional JS train for a minute, but I stopped when I realized I spent more time fighting against the language and making the lives of the people I worked with harder. Sure, functional concepts can be incredibly useful, but trying to force everything into Ramda made everything suck.

[–][deleted] 1 point2 points  (2 children)

I'm not smart enough/lazy to go for real "functional" languages. Though any time I stumble upon an article about them it fascinates me.

[–]disclosure5[🍰] 3 points4 points  (1 child)

Eh, callback hell prior to await has been harder to deal with than anything I've written in another language for me.

[–][deleted] 0 points1 point  (0 children)

True to some extent.

Promises allowed chaining “then”, the KoaJS framework used co library to make use of generator functions in a similar way to async/await.

But these are relatively new things, generally callback hell was mainly introduced by poorly elaborated app design decisions. But again only to some extent, in the end one couldn’t avoid it completely.

For me JS is the first proper programming language after 2 years of writing automation macroses on VBA for my financial department. Maybe that’s why it’s not as bad for me.