home.social

#rxnet — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rxnet, aggregated by home.social.

  1. Update on the future of Rx.NET versioning:
    github.com/dotnet/reactive/dis

    The 3 scenarios that seemed to prevail:

    1. Keep the System.Reactive packages. Solve problems using hacks (different API surface in build time than in runtime).

    2. Introduce System.Reactive.Net packages, keep System.Reactive as a facade.

    3. Try the first one in Rx7. If (when?) something breaks, switch to the second one.

    A YT summary:
    youtube.com/watch?v=GSDspWHo0bo

    #dotnet #rx #rxnet #reactive #reactiveprogramming

  2. The State of Rx.NET in 2025

    youtube.com/watch?v=SZpmj0fSfFI

    tl;dw:

    - Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

    - AsyncRx.NET will be developed over time.

    - Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

    #rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

  3. The State of Rx.NET in 2025

    youtube.com/watch?v=SZpmj0fSfFI

    tl;dw:

    - Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

    - AsyncRx.NET will be developed over time.

    - Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

    #rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

  4. The State of Rx.NET in 2025

    youtube.com/watch?v=SZpmj0fSfFI

    tl;dw:

    - Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

    - AsyncRx.NET will be developed over time.

    - Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

    #rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

  5. The State of Rx.NET in 2025

    youtube.com/watch?v=SZpmj0fSfFI

    tl;dw:

    - Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

    - AsyncRx.NET will be developed over time.

    - Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

    #rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

  6. The State of Rx.NET in 2025

    youtube.com/watch?v=SZpmj0fSfFI

    tl;dw:

    - Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

    - AsyncRx.NET will be developed over time.

    - Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

    #rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

  7. Today I don't have any F# bits as I was in a bunch of meetings so... Let's feature another F# library!
    Today we have : Fsharp.Control.Reactive
    https://github.com/fsprojects/FSharp.Control.Reactive
    If you like rxjs/rxjava/rxnet then this is a library to look after!
    It enables reactive functional programming over observables and subjects, I personally love this library quite a lot


    #fsharp #dotnet #rx #frp #functionalreactiveprogramming #reactive #rxjs #rxnet

  8. Loving Rx.​NET interoperability with Tasks.

    Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

    In other cases I do filtering, throttling, debouncing on a merged stream of events.

    #rxnet #dotnet #reactivex

  9. Loving Rx.​NET interoperability with Tasks.

    Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

    In other cases I do filtering, throttling, debouncing on a merged stream of events.

    #rxnet #dotnet #reactivex

  10. Loving Rx.​NET interoperability with Tasks.

    Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

    In other cases I do filtering, throttling, debouncing on a merged stream of events.

    #rxnet #dotnet #reactivex

  11. Loving Rx.​NET interoperability with Tasks.

    Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

    In other cases I do filtering, throttling, debouncing on a merged stream of events.

    #rxnet #dotnet #reactivex

  12. Loving Rx.​NET interoperability with Tasks.

    Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

    In other cases I do filtering, throttling, debouncing on a merged stream of events.

    #rxnet #dotnet #reactivex

  13. It’s alive!
    Well, kinda… I still need to figure out the images, improve the layout, and fix the navigation.
    But this is already my first + project :) (Not THAT different from , but there are a fill things to learn)