|almost 6 years ago
|about 22 hours ago
|Apache License 2.0
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Is it a good idea to use Google Guava library for Android development?
2 projects | /r/codehunter | 15 May 2023
I am involved in the development of Android application which is a rather "thick" mobile client for a Web service. It heavily communicates with the server but also has a lot of inner logic too. So, I decided to use some features of Google Guava library to simplify development process. Here is a list of features I'm very interested in: immutable collections, base utils, collection extensions, functional programming sugar and idioms (common.collect and common.base), primitives utilities (common.primitives), hashing utilities (common.hash), concurrent utils (futures and AsyncFunction). Things I don't want to use in Android: common.cache (see question below), common.eventbus (we have better Android specific libs for this, such as Otto), common.io (we can use okio for Android now).
EventBus 3.1 with plain Java support
3 projects | news.ycombinator.com | 19 Jun 2021
1. I'm happy to see that EventBus has made this change. Let's hope the long overdue AndroidX migration (we're three years into AndroidX, folks) follows close on its heels.
2. Event buses are really, really bad. (At least, this kind of event bus is) The Android community has some battle scars on this, so I'll drop a little history for the broader audience here.
Event buses were an architectural fad that were briefly explored to address the challenges of communicating in the immature application architectures of the era. The maintenance lifetime of Otto, a competing event bus, is a good reference point for when they might have been considered reasonable practice: 2012 through 2015: https://github.com/square/otto/tags
This tool was abandoned by leading edge shops when they saw how rapidly it could make a complete hash of any thoughtfully laid out architecture. Connections made in an EventBus based application tend to be many-to-many, without the sender of an event having a direct reference to its recipient or vice versa. This is incredibly irritating to debug, and breeds communication patterns that are challenging even in a disciplined codebase. In an _undisciplined_ codebase they can be breathtakingly byzantine, even in small scale development.
Instead of using this, many leading edge shops started switching to RxJava at around 2016. RxJava is a powerful tool with sharp edges and a steep learning curve, but the need was so imminent and the failings of the existing EventBus-style tools so clear that it caught on. Indeed, while Google understandably felt it RxJava was too complex to recommend as an introductory tool, their first party LiveData tool released a few years later was essentially RxJava with the edges sanded off.
Of course, we're not even further down the road than that. Kotlin coroutines presents its own paradigm shift to contend with, but it's a clear step up from all the other solutions, and has Google's blessing as well. There's not much reason to start new development on top of anything except coroutines.
So where does that leave EventBus?
EventBus is at this point about as legacy as you can get without going all the way back to AsyncTask. Anytime I'm doing a code audit and see this dependency, red flags immediately go up: not only is it a sign that this code is far behind the times, but it's also a flag that I'm going to find some truly unfortunate and problematic design decisions.
People need what they need, and it's of course good to see critical dependencies for legacy applications get upgrades. But I can't recommend strongly enough to avoid this tool.
Humble Chronicles: Managing State with Signals
4 projects | /r/Clojure | 16 May 2023
Is this similar RxJava, the reactive extensions library for https://github.com/ReactiveX/RxJava ? I have made that work in Clojure in production.
How to do threading in Android.
2 projects | /r/androiddev | 24 Mar 2023
Since you mentioned java, there is RxJava and RxAndroid. Google general recommendation now is to use kotlin coroutines if you're considering writing your app with that.
must known frameworks/libs/tech, every senior java developer must know(?)
6 projects | /r/java | 9 Dec 2022
You all beat me to MapStruct and Testcontainers. Honorable mention to RxJava, which I use in Desktop apps.
What is your tech stack?
4 projects | /r/androiddev | 14 Sep 2022
RxJava with RxRelay (and rx-combinetuple-kt)
Best libraries for Android Developers
19 projects | dev.to | 15 Jul 2022
What are the most common used (3rd party) libraries and frameworks used in Android development?
30 projects | /r/androiddev | 7 Jan 2022
Concurrency: Kotlin coroutines for general use, Rx or Flow for reactive programming (you can technically use Rx for regular concurrency as well, but not really what it's meant for)
When consuming from a reactive stream is it more like a literal stream where items in the stream ay go by and not get consumed while you're busy, or is it more like a queue?
2 projects | /r/learnjava | 3 Aug 2021
In big words, kafka and rxJava are 2 different things, with kafka you transport data, produce and consume messages, then you can process them however you want. Rx java helps you write asynchronous code and it's no queue/topic related. You can read more here
MVVM Architecture On HarmonyOS Using Retrofit And RxJava
3 projects | /r/HuaweiDevelopers | 29 Mar 2021
Backpressure in Reactive Systems
3 projects | dev.to | 14 Mar 2021
This post provides information on backpressure in general and how RxJava (v3), Project Reactor and Kotlin's Coroutines handle it.
Functional Programming in Java, Explained
2 projects | dev.to | 14 Dec 2020
Both of the most popular Java Reactive libraries, RxJava and Reactor, are based on Java 8 Streams API, which means they also use functional interfaces in their code.
What are some alternatives?
Mutiny - An Intuitive Event-Driven Reactive Programming Library for Java
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
EventBus - Event bus for Android and Java that simplifies communication between Activities, Fragments, Threads, Services, etc. Less code, better quality.
Reactive Streams - Reactive Streams Specification for the JVM
RxAndroid - RxJava bindings for Android
rsocket-java - Java implementation of RSocket
AndroidEventBus - A lightweight eventbus library for android, simplifies communication between Activities, Fragments, Threads, Services, etc.
reactor-core - Non-Blocking Reactive Foundation for the JVM