language-ext VS ReactiveUI

You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).

Language-Ext is my personal favourite, but it can be a bit overwhelming for beginners due to its extensive feature set

> but I just want something closer to Scala, but for .Net

That's what I'm working toward with my language-ext library [1]. Obviously more support for expression based programming would be welcome (and higher kinds), but you can do a lot with LINQ and a good integrated library surface.

[1] https://github.com/louthy/language-ext

Definitely a fan of option types, I wonder this library has anything over the C# library language-ext which also has an Option type?

Hey, I am considering adopting the Result pattern in my codebase. Wanted to get some opinions from someone who has experience with it: should I start with language-ext or FunctionalExtensions?

> [1] https://github.com/louthy/language-ext

Cool library. I've had a few of these patterns in my Sasa library for years, but you've taken it to the Haskell extreme! Probably further than most C# developers could stomach. ;-)

You might be interested in checking out the hash array mapped trie from Sasa [1]. It cleverly exploits the CLR's reified generics to unbox the trie at various levels which ends up saving quite a bit of space and indirections, so it performs almost on par with the mutable dictionary.

I had an earlier version that used an outer struct to ensure it's never null, similar to how your collections seem to work, but switched to classes to make it more idiomatic in C#.

I recently started sketching out a Haskell-like generic "Deriving" source generator, contrasted with your domain-specific piecemeal approach, ie. [Record], [Reader], etc. Did you ever try that approach?

[1] https://sourceforge.net/p/sasa/code/ci/default/tree/Sasa.Col...

[2] https://sourceforge.net/p/sasa/code/ci/57417faec5ed442224a0f...

languageext supports linq for its monads and I kinda love it. The challenge is convincing my colleagues. 😅

language-ext supports it and it's pretty dang cool.

I can only recommend c# language extensions library https://github.com/louthy/language-ext

ReactiveUI is based on Rx and very popular in the .Net world: https://www.reactiveui.net/.

I use PropertyChanged.Fody all the time and it works fantastically and consistently for implementing INotifyPropertyChange. It is even smart enough to understand dependencies within your get/set functions (should you choose to have custom ones) and notify that property if any of it's dependent properties change. While we are on the subject, if you are using MVVM with observables, you should really check out ReactiveUI. It is wonderful.

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

My favorite framework is Reactive UI but it's a bit more advanced than most MVVM frameworks since it uses Reactive Programming. You can still try its most basic features, though.

There is a lot of overlap between WPF and Avalonia so I would start with either one of those. Most certainly Avalonia if you plan to do cross platform dev. I would also highly recommend that you learn and conform to MVVM and dependency injection for your architecture in order to write clean, maintainable, and testable code. My recommendation is ReactiveUI. It leans heavily on more modern patterns like Reactive extensions and IObservable and it can do so much more than just MVVM. As such, it is also very similar to Angular so the concepts will transfer easily if you ever need to do web development. On a side note, Pluralsight has a nice quick course on SOLID design principles. If your code is a mess, it would be a good idea to take a course on this though learning MVVM will be a big step in the right direction.

Also, about data binding and reactivity if you really enjoy WinForms, nevar forget!! https://www.reactiveui.net

Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).

Some projects like ReactiveUI take on a more webapp style project structure, with resources being in some static resources folder and all code being in a src folder.