RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
-
Updated
Sep 18, 2020 - Java
{{ message }}
RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
The complete guide to static typing in "React & Redux" apps using TypeScript
A powerful obfuscator for JavaScript and Node.js
Entire React code base explanation by visual block schemes (Stack version)
Make. It. Bounce.
An open source real-time network topology and protocols analyzer
A polyglot web converter.
Differences between Flowtype and TypeScript -- syntax and usability
The BGP swiss army knife of networking
RxFlow is a navigation framework for iOS applications based on a Reactive Flow Coordinator pattern
A goal, task & habit tracker + personal dashboard to focus on what matters
Ideas:
Free, open source mental health communication web app to share experiences with loved ones
HOMER - 100% Open-Source SIP / VoIP Packet Capture & Monitoring
I'm trying a simple test with tcpliveplay but it seems tcpliveplay doesn't handle TCP handshake properly.
Let me describe the steps from my testing.
# tcpdump host 104.31.95.22 -n -s 65535 -w http.pcap
RAEairfoil_AUSM_issue.pdf
Describe the bug
I was trying to run RAE2822 rans case with AUSM scheme (SU2-7.0.1). I observed some issue while using Venkatakrishnan or Venkatakrishnan-Wang limiter, spurious pressure distribution over the surface along with pressure contours in the field are observed. While with Van Albad
MVVM + Kotlin + Retrofit2 + Dagger2 + Coroutines + MVP + Kotlin-Android-Extensions + RX-java + Mockk + Espresso + Junit5
Add a description, image, and links to the flow topic page so that developers can more easily learn about it.
To associate your repository with the flow topic, visit your repo's landing page and select "manage topics."
Documentation Issue
The diagram legend at the top of the Flux/Mono javadoc page is awesome. However, the legend only mentions a very simple use case, and there are many other symbols used in the method diagrams that do not appear in the legend.
Improvement Suggestion
It would be super-awesome if the legend included all symbols used in the method diagrams.
For example: