Ramda.js — библиотека, которая избавит вас от reduce и map-каши
Привет, Хабр! Если вас когда-либо раздражало, что Array.prototype.map нельзя использовать для объектов или reduce постоянно требует передавать начальное значение, Ramda.js решает эти проблемы, делая код чище, декларативнее и удобнее. Ramda — это библиотека для функционального программирования в JavaScript, которая по умолчанию не мутирует данные и поддерживает каррирование. В отличие от Lodash, где функциональность чаще заточена под удобство, Ramda больше ориентирована на чистоту кода и прогнозируемость работы функций.
Got a resume this morning that was Scott Sauyet's with the name changed and some stuff added (badly, in a different font).
It first piqued my interest because they claimed to be one of the founders of #Ramda, which I know of and use.
I dunno how anyone could think they'd get away with this?
I recently wrote about what I think is a sensible front-end stack for large production applications.
Check it out here: https://gar.dev/posts/a-sensible-front-end-stack-for-production-applications-2023-edition
#typescript 4's variadic tuple types looks like a huge win for fp oriented libraries such as #ramda #fp-ts or #purify !
Can't wait for someone to get busy and refactor the existing typings for those libs.
@e8johan Great talk on FP in JS using ramda.
I've been trying to introduce more FP in my code (Typescript) aside from the regular map/filter/reduce/...
But I think I got in too deep trying to use the great fp-ts [1], it's just a lot when you only have a basic FP background.
Thanks for sharing that video, I think I'll stick with #ramda for now.
@natecull @alper definitely liked #ramda more than #lodash or the others. #Rambda is new to me.
There's also the fantasy land compliant~ libraries, which give you all the functional #CategoryTheory stuff, but I found it was hard to use inside #typescript / #javascript .