#reactivex — Public Fediverse posts

Hey programmers!
In your opinion, is ReactiveX (framework across multiple languages and platforms implementing the observer pattern) _functional_ reactive programming (FRP)?

I'm aware of the official statement in the docs, and I have my own opinion, but I've also seen some people disagree with both, so I'm curious about your reasoning.

#programming #reactivex #dotnet #javascript #csharp #closure #java #scala #python #ruby #cpp

Hey programmers!
In your opinion, is ReactiveX (framework across multiple languages and platforms implementing the observer pattern) _functional_ reactive programming (FRP)?

I'm aware of the official statement in the docs, and I have my own opinion, but I've also seen some people disagree with both, so I'm curious about your reasoning.

#programming #reactivex #dotnet #javascript #csharp #closure #java #scala #python #ruby #cpp

Hey programmers!
In your opinion, is ReactiveX (framework across multiple languages and platforms implementing the observer pattern) _functional_ reactive programming (FRP)?

I'm aware of the official statement in the docs, and I have my own opinion, but I've also seen some people disagree with both, so I'm curious about your reasoning.

#programming #reactivex #dotnet #javascript #csharp #closure #java #scala #python #ruby #cpp

Hey programmers!
In your opinion, is ReactiveX (framework across multiple languages and platforms implementing the observer pattern) _functional_ reactive programming (FRP)?

I'm aware of the official statement in the docs, and I have my own opinion, but I've also seen some people disagree with both, so I'm curious about your reasoning.

#programming #reactivex #dotnet #javascript #csharp #closure #java #scala #python #ruby #cpp

Hey programmers!
In your opinion, is ReactiveX (framework across multiple languages and platforms implementing the observer pattern) _functional_ reactive programming (FRP)?

I'm aware of the official statement in the docs, and I have my own opinion, but I've also seen some people disagree with both, so I'm curious about your reasoning.

#programming #reactivex #dotnet #javascript #csharp #closure #java #scala #python #ruby #cpp

#Async #Rust is like #ReactiveX on a systems level with full control over the #concurrency!

https://en.wikipedia.org/wiki/ReactiveX

#RustLang

#Async #Rust is like #ReactiveX on a systems level with full control over the #concurrency!

https://en.wikipedia.org/wiki/ReactiveX

#RustLang

#Async #Rust is like #ReactiveX on a systems level with full control over the #concurrency!

https://en.wikipedia.org/wiki/ReactiveX

#RustLang

#Async #Rust is like #ReactiveX on a systems level with full control over the #concurrency!

https://en.wikipedia.org/wiki/ReactiveX

#RustLang

#Async #Rust is like #ReactiveX on a systems level with full control over the #concurrency!

https://en.wikipedia.org/wiki/ReactiveX

#RustLang

#Java has its IO implementations. Multiple, actually. They don't have the same properties or ergonomics as #Scala's IO (e.g., flatMaps are not optimized for tail-recursion). People may not like it, but they are deployed at scale.

Here's what #Spring WebFlux uses:
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Mono.html

Here's the venerable #ReactiveX (#RxJava): https://reactivex.io/documentation/single.html

#Java has its IO implementations. Multiple, actually. They don't have the same properties or ergonomics as #Scala's IO (e.g., flatMaps are not optimized for tail-recursion). People may not like it, but they are deployed at scale.

Here's what #Spring WebFlux uses:
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Mono.html

Here's the venerable #ReactiveX (#RxJava): https://reactivex.io/documentation/single.html

#Java has its IO implementations. Multiple, actually. They don't have the same properties or ergonomics as #Scala's IO (e.g., flatMaps are not optimized for tail-recursion). People may not like it, but they are deployed at scale.

Here's what #Spring WebFlux uses:
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Mono.html

Here's the venerable #ReactiveX (#RxJava): https://reactivex.io/documentation/single.html

#Java has its IO implementations. Multiple, actually. They don't have the same properties or ergonomics as #Scala's IO (e.g., flatMaps are not optimized for tail-recursion). People may not like it, but they are deployed at scale.

Here's what #Spring WebFlux uses:
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Mono.html

Here's the venerable #ReactiveX (#RxJava): https://reactivex.io/documentation/single.html

#Java has its IO implementations. Multiple, actually. They don't have the same properties or ergonomics as #Scala's IO (e.g., flatMaps are not optimized for tail-recursion). People may not like it, but they are deployed at scale.

Here's what #Spring WebFlux uses:
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Mono.html

Here's the venerable #ReactiveX (#RxJava): https://reactivex.io/documentation/single.html

#reactivex on #dotnet is actually really fun to use, especially with #linq method style syntax

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

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

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

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

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

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

@Perl @gandalf’s RxPerl will cure what ails you, if what ails you is dealing with streams of data via asynchronous callback functions. https://metacpan.org/pod/RxPerl

You can drop it into your existing event-driven #Perl code with ease, as it works with @leonerd’s IO::Async, @mojolicious’s Mojo::IOLoop, and AnyEvent interface libraries. It’s an implementation of #ReactiveX designed to behave like #JavaScript’s #RxJS. https://noc.social/@gandalf/109839670728579860

@Perl @gandalf’s RxPerl will cure what ails you, if what ails you is dealing with streams of data via asynchronous callback functions. https://metacpan.org/pod/RxPerl

You can drop it into your existing event-driven #Perl code with ease, as it works with @leonerd’s IO::Async, @mojolicious’s Mojo::IOLoop, and AnyEvent interface libraries. It’s an implementation of #ReactiveX designed to behave like #JavaScript’s #RxJS. https://noc.social/@gandalf/109839670728579860

@Perl @gandalf’s RxPerl will cure what ails you, if what ails you is dealing with streams of data via asynchronous callback functions. https://metacpan.org/pod/RxPerl

You can drop it into your existing event-driven #Perl code with ease, as it works with @leonerd’s IO::Async, @mojolicious’s Mojo::IOLoop, and AnyEvent interface libraries. It’s an implementation of #ReactiveX designed to behave like #JavaScript’s #RxJS. https://noc.social/@gandalf/109839670728579860

@Perl @gandalf’s RxPerl will cure what ails you, if what ails you is dealing with streams of data via asynchronous callback functions. https://metacpan.org/pod/RxPerl

You can drop it into your existing event-driven #Perl code with ease, as it works with @leonerd’s IO::Async, @mojolicious’s Mojo::IOLoop, and AnyEvent interface libraries. It’s an implementation of #ReactiveX designed to behave like #JavaScript’s #RxJS. https://noc.social/@gandalf/109839670728579860

@Perl @gandalf’s RxPerl will cure what ails you, if what ails you is dealing with streams of data via asynchronous callback functions. https://metacpan.org/pod/RxPerl

You can drop it into your existing event-driven #Perl code with ease, as it works with @leonerd’s IO::Async, @mojolicious’s Mojo::IOLoop, and AnyEvent interface libraries. It’s an implementation of #ReactiveX designed to behave like #JavaScript’s #RxJS. https://noc.social/@gandalf/109839670728579860