ada-spark-rfcs VS Rx.NET

Original discussion was there, I guess you can post your comments to that PR to keep the discussion in one place.

I forgot where I saw it, but I do recall reading somewhere that the ARG had discussed whether a shorter revision cycle would be better or not. I wouldn't be surprised if the creation of this ( https://github.com/AdaCore/ada-spark-rfcs ) was inspired by that discussion.

Ada might be getting pattern matching soon too:

https://github.com/AdaCore/ada-spark-rfcs/blob/master/protot...

> I did some ADA in the past and yes, it is a nice language, but it lacks the modernity and a dynamic community like Rust. ADA did received some nice update to its specification, but, just like C++, it struggle / cannot really fit the latest innovation in programming language that easily.

I'm still learning both Ada and Rust, nevertheless I humbly disagree. The more I learn it and other "old" languages the more it looks to me like "modern" ones rediscover things that have been present in other languages for years.

The really significant difference I can see for now is that Ada is not focused so strongly on functional programming paradigm. Rust borrow checker is a strong success of course and was another significant difference, but latest SPARK got borrow checking capabilities too, AFAIK.

While Ada's open-source community is smaller, I find it as energetic and devoted to improving the ecosystem as Rust's. I have no idea about closed-source community, but in the past 4 years ArianeGroup [1], Airbus [2] and Nvidia [3] talked about choosing Ada for their high-integrity applications.

> And to be fair, it is fine. ADA is very much a "committee" language (its spec are ISO/IEC) instead of a "community" language (all the spec and rfc of Rust are on github and anyone can easily discuss them).

You can discuss Ada/SPARK RFCs here: https://github.com/AdaCore/ada-spark-rfcs . I think I once saw on Ada forum or chat that someone proposing changes to the language was simply invited to talk to people working on the standard, so it doesn't look like the language is developed in isolation or something.

> This makes it so that ADA doesn't get the attention, and the rapidity of innovation, that a language like Rust does, but ADA is mostly made for program that will need to be maintained in critical operations for decades with the code being maintainable and compilable far into the future.

I think that Ada adopted quiet quickly to standards set by Rust: lower entry barrier toolchain, compelling licensing, library distribution, RFCs, etc. And in terms of language features, in many areas it's not only on par, but ahead of competition. So you're less likely to see lots of changes, but they do happen nevertheless. I'm not saying Ada is perfect, of course. There are parts of it that other languages do better. No shame in that.

IMHO, the reason Ada is unknown to many people is a combination of its past, myths surrounding it, and general trend of people to follow trends. ;) But I currently find Ada/SPARK even more compelling option than Rust, even though I like both.

[1] https://www.facebook.com/ArianeGroup/posts/2872955946126067

There's a proposal to allow dot syntax for untagged types as well.

There's also an active discussion about adding format strings to the language here: https://github.com/AdaCore/ada-spark-rfcs/pull/77

DynamicData is a .NET library that brings the power of reactive programming to collections. It is built upon the principles of Reactive Extensions (Rx), extending these concepts to handle collections like lists and observables more efficiently and flexibly. DynamicData provides a set of tools and extensions that enable developers to manage collections reactively, meaning any changes in the data are automatically and efficiently propagated through the application.

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.