自分の中で理由は完全に説明できないけど、たとえばkoinはJavaから使ってもJava側が無茶苦茶なコードにならない（インターフェースを先に書いておけば、koinはSupplier以上以下でもないから）混ぜてもいいけど、coroutineとかはヤバそうなのでRxJavaみたいなJavaで動く非同期に合わせたほうがいい？

Kotlin coroutines changed how I think about async code entirely. Developers still reaching for RxJava in 2024 need to seriously reconsider their life choices 😄 the learning curve is worth it, trust me.

#hms #relationship #disruptor #allocator #oomkiller #rxjava I think I got closer why the "Relationship Disruptor" prevents or cancels any meaningful relationship formation/continuation of me, despite on paper, my stats and dynamically discoverable fetures are fine. ~~~~ Hint was the RxJava issue with groubBy excursions and the linux out-of-memory process killer plaguing GitHub many years ago. The main drawback with groupBy is that a new item may trigger a new group creation or feed one of the existing group, while they are being backpressured. There is no way to know upfront without introducing latencies and deadlocks. The solution I'm going to implement with RxJava 4 is a buffer for group creation excursions, default 4x of the main prefetch amount. So if the item->group dispatch is relatively balanced, progress can be made on the more frequent groups. When the buffer gets full, the operator switches to LRU group closing, meaning older unused groups get completed and their slot is reused for the new group. This of course requires losing the group reference identity and treat the group as a 'value stream' itself. As for the OOMKiller, it was partly systematically fixed by natively giving the CI/CD more memory, as well as we updated many tests to use less memory, the pipeline to use caching and other small test optimizations. ~~~~ What does it have to do with my relationship establishing issues? When I see a candidate, my mind starts doing heavy processing: simulations, evaluations, getting all past experience, data, skills loaded into working memory, which causes a huge spike in memory requirements by the ledger. Since the process is not very data efficient and mostly not async, it adds further burden on the conformal compactor during the process to save up on memory before more allocation is needed. This all spends huge amounts of entropy and risks process cancellation due to local bulk-boundary instability. In layman terms, I make some peculiar face while processing which is often off-putting and the time it takes to get some early results makes the initital meeting opportunity window gone, decohered of hard limited. So the solution is, optimization, zero-copy solutions, async loading, dynamic-adaptive loading, past history and experience compaction for quicker wibe processing at least. This is doable and a similar thing already happened many years ago with my local quantum search capability (Orch-OR collapse NN processing improvements). I have to post the search query and it does it asynchronously with optional progress or partial result retrieval. It is very efficient and high quality usually. Think of it like posting on X and the X algorithm routing interesting topics back to me via 'For You' without me needing to refresh every 0.5 seconds. Wir werden schaffen das! 🫡

Thanks to RxJava-CombineTuple-Kt, it actually resulted drastically simpler code at the time than what most other apps I've found were doing. github.com/Zhuinden/rx-combi…

I've been waiting for explicit backing fields since Kotlin v1.7.0, although I had a better use-case for them when I was using RxJava (BehaviorRelay<T> exposed as Observable<T> so that you don't have to use .hide()), same with MutableLiveData back when, but not MutableStateFlows.

Fail early, fail often. Put the self-verification test upfront in the RxJava build pipeline in case I make a mistake, the build fails in 1.5 minutes instead of 7 minutes running the full tests in futility. github.com/ReactiveX/RxJava/…

MVVMTemplate, Android project template Splits Compose app code into app, build-logic, core, and feature modules with runtime RxJava/Coroutines selection

Three dev books published between 2015 and 2017. RxJava Essentials with Packt. Grokking ReactiveX with Manning. The royalty checks now pay for less than my monthly coffee. But every job offer, every speaking invite, every CTO conversation I've had in a decade traces back to those books.

Top tech skills to have in your CV in 2026 1. Distributed Caching : Redis, Memcache 2. Monitoring : Splunk, Dynatrace, Grafana, ELK 3. Messaging : Kafka, JMS, RabbitMQ 4. Testing : TDD, Mockito, JUnit 5. CI/CD & Containers : Jenkins, GitHub Actions, Docker, Kubernetes 6. Frameworks : Spring Boot, Spring MVC, Apache Camel 7. Microservices : Config Server, API Gateway, Service Discovery, Resilience4j 8. Multithreading & Concurrency : Executors, ForkJoin, CompletableFuture 9. Security : Spring Security, OAuth2, JWT 10. Persistence : Hibernate, JPA, MyBatis 11. API Development : REST, Swagger, OpenAPI 12. Reactive Programming : WebFlux, RxJava, Reactor 13. Build Tools : Maven, Gradle 14. Code Quality : SonarQube, PMD, Checkstyle 15. Cloud : AWS, GCP, Azure 16. Java Versions : Java 8:25 features 17. Design Principles : SOLID, Design Patterns, Clean Architecture

The tensor network operates on entanglement and ER=EPR bridges, or attention pointers. It already is capable of hallucination free operation: - the lack of a pointer; - like having two nodes and several paths pointing to the same other node, or - the pointer is colored all already included in the reasoning math. Maybe I haven't expressed it explicitly so far, sorry. Seems trivial to me after working with RxJava. The thing is, "no answer" is often so unsatisfying, you'd rather ask the network to "okay, give me your best guess anyways".

I once commented somewhere or told Grok I'm still single and bad outlook. Algorithm did the rest. Now I'm trying to debug relationship formation failures and relationship failures to figure out why self-improvement yielded zero gradient for me. You know, you debug RxJava with RxJava. X relationship anecdotes with X relationship counter-anecdotes to trigger crashout and/or get valuable logs.

How did you even end up on this section of 𝕏 anyway (on your RxJava account)?

What would you have chosen for this one? Today’s android codebase is full of abstraction, ngl. That app could have functioned with like 3 modules - the two apps and a shared module. With that, I may not need to write convention plugins, or even baseline profiles and benchmarks to improve app startup and JIT compilation (though today compose ships with baseline profiles*) Dagger2 can replace hilt, sqlite for room, views for compose, rxjava for coroutines, controller for viewmodel, etc but with additional boilerplate to maintain and missing out on important capabilities. But, such approach would raise questions which I may not answer. Also, it addresses several issues as well, some of which are documented here developer.android.com/topic/… Most codebases I have interacted with recently look like that. I did my architectural benchmark on Now in Android (Android’s reference app) github.com/android/nowinandr… Of course I can defend my architectural decisions beyond ‘this is what Android engineers know’ And was thinking of spending some time to talk about it as I build.

MovieGuide, Android Clean Architecture sample app Combines MVP, RxJava, and Dagger 2 in a movie app with trailers and reviews Not actively maintained; README does not recommend Rx anymore

My 2026-beginner stack: 📱 Kotlin Jetpack Compose 💉 Hilt (DI) 🌐 Retrofit (networking) 💾 Room (local DB) ⚡ Coroutines Flow 📂 DataStore (NOT SharedPreferences) 🧭 Compose Navigation Skip RxJava. Skip raw Dagger. Skip everything pre-2022.

Published 3 dev books with Packt and Manning. RxJava Essentials, Grokking ReactiveX, Embedded Android. Today my open-source skills have 1k GitHub stars. Books were how we shared knowledge then. Skills are how we share it now. The act of teaching out loud is what compounds.

A new AI review! cn-ljb/rxjava_for_android ⭐2.8/5.0 This repository is an Android demo project showcasing RxJava usage (primarily RxJava 1.x) across common UI and app scenarios: click streams via RxBinding, operators like buffer/z... gitrated.com/cn-ljb/rxjava_f…

Contrast first: I like AI writing but hate AI code. Only let AI produce small snippets of code. I'm very good at coding myself and expert in my field way beyond most AIs. Example: RxJava. AIs are retarded in this regard and they actually work off *my* blog posts about RxJava. Ridiculous suggestions I get like "contact @akarnokd for assistance". No sh|t. But I'm not good at explaining RxJava for mere mortals, but AI can frame the code and changes way approachable to all.

Java / JVM Java Collections, java.io, java.nio, java.net, java.time, java.util.concurrent, Swing, AWT, JavaFX, Jakarta EE, Servlet API, JSP, JSF, JPA, JAXB, JAX-RS, Spring Framework, Spring Boot, Spring Security, Spring Data, Spring Cloud, Hibernate, EclipseLink, MyBatis, jOOQ, HikariCP, Apache Commons, Commons Lang, Commons IO, Commons Codec, Commons Collections, Commons Math, Guava, Jackson, Gson, Moshi, JSON-B, JSON-P, Log4j, Logback, SLF4J, JUL, Netty, Undertow, Jetty, Tomcat, Grizzly, Vert.x, Akka, Quarkus, Micronaut, Helidon, Dropwizard, Play Framework, Vaadin, JUnit, TestNG, Mockito, AssertJ, Hamcrest, Spock, Cucumber JVM, Arquillian, Maven, Gradle, Ant, Lombok, MapStruct, AutoValue, Immutables, Dagger, Guice, H2, HSQLDB, Derby, JDBC drivers, Flyway, Liquibase, Kafka clients, RabbitMQ Java client, JMS, Camel, CXF, Jersey, RESTEasy, OkHttp, Retrofit, Feign, Reactor, RxJava, Project Loom libraries, Kotlin stdlib, kotlinx.coroutines, Ktor, Exposed, Arrow KT.

I actually don't know what the Android community "senior members" are doing nowadays. I spend most of my time with app maintenance, each app its own snippet in time. One of them is Kotlin EventBus. Other is Java RxJava. I feel most other "old" members left social platforms.