Rx.NET VS ramda

One of the greatest things i discovered recently, is Reactive programming / Reactive Extensions ( https://github.com/dotnet/reactive ).

https://github.com/dotnet/reactive has a lot of different time related extensions for "events". Maybe you'll find something for yourself, if you google for rate limiting with reactive.

Install Reactive Extensions: https://github.com/dotnet/reactive

Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read.

I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.

If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.

We'd really appreciate if it consumers of the library could update and provide any issues / bugs via the GitHub repo: https://github.com/dotnet/reactive/issues

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!)