stdlib VS ramda

Numpy is a library - node.js has plenty of them, what is missing? There is stdlib package that offers optimized math functions, for example.

Websites do the same thing as 15 years ago? Not true, websites can now exceed desktop apps. Was their figma 15 years ago?

20 times more complex - this comes with doing more. 15 years ago there was no CI/CD.

Write CSS - don’t have to given Sass, components, and bootstrap.

Performance is worse - look at v8 benchmarks, look at webgl and Wasm. The browser itself can run much faster today, and people are doing more with it.

JS barebones - just one package. https://github.com/stdlib-js/stdlib. - and the node ecosystem is a feature not a bug.

Look elsewhere - every other UI framework we’ve tried before has been worse in terms of compatibility, functionality, flexibility, and available prebuilt tooling.

two of the best PRNG libs for JS/TS: https://github.com/transitive-bullshit/random and https://github.com/stdlib-js/stdlib

Scientific calculations - like what? There is a stlib package for JS where CPU hungry parts are written in C.

lodash and lodash-es for browser are good, check out also stdlib

> I wonder why there is not a simple math lib

This [0] might be what you are looking for, it has both is-number and is-odd.

[0] https://github.com/stdlib-js/stdlib

JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/

It’s fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.

But it’s good practice for understanding combinators which is useful for some kinds of problems.

This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)

https://ramdajs.com/

To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.

Other libraries to check out are pratica and ramda

I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes

I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.

Lodash gets so many things wrong I’d rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read

[1] https://ramdajs.com/

Do note though that ramda is different from rambda. 👍 (Granted they are very similar!)