Why Not RxLifecycle?
Hello. This is Dan Lew. You may or may not know me as the author of RxLifecycle. Here’s why I’ve started pulling back from using my creation. Origins When Trello first started using RxJava, we were dismayed with how easy it was to leak memory when using it. Seemingly any Subscription you setup would leak unless you explicitly cleared it. As such, we were constantly juggling Subscriptions and unsub
Model View Whatever + Rx ã®ã‚¢ãƒ³ãƒãƒ‘ターン - Re.Ra.Ku tech blog
GUIアーã‚テクãƒãƒ£ãƒ‘ターンã¨ã—ã¦Model View Whateverを採用ã—ãŸéš›ã«ã€Rxã®ã‚¹ãƒˆãƒªãƒ¼ãƒ をプレゼンテーション層ã‹ã‚‰ãƒ¢ãƒ‡ãƒ«å±¤ã¾ã§ä¸€æ°—通貫ã§ã¤ãªã’ã¦ã—ã¾ã†ã®ã¯ã‚¢ãƒ³ãƒãƒ‘ターンã§ã‚ã‚‹ã€ã¨ã„ã†è©±ã‚’ã—ã¾ã™ã€‚ å‰æ GUIアーã‚テクãƒãƒ£ãƒ‘ターンã«ãŠã‘ã‚‹ Model View Whatever パターンã€ã¨ãã«MVVMã«è¿‘ã„パターンをå‰æã¨ã—ã¾ã™ã€‚ã„ã‚ゆるサーãƒã‚µã‚¤ãƒ‰ã®ã€Œwebç³»MVCã€ã¯å‰æã¨ã—ã¾ã›ã‚“。 Model View Whateverパターンã¨PDS ãã‚‚ãã‚‚GUIアプリケーションã§Model View Whateverã¨ã„ã†ã‚¢ãƒ¼ã‚テクãƒãƒ£ãƒ‘ターンを採用ã™ã‚‹ç†ç”±ã¨ã—ã¦ã€PDSã®å®Ÿç¾ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ã‚ãŸã‚Šã®è©±ã¯è©³ã—ãã¯å®Ÿæ³ä¸ç¶™ã‚·ãƒªãƒ¼ã‚º Vue.jsã§å®Ÿç¾ã™ã‚‹MVVMパターン Fluxアーã‚テクãƒãƒ£ã¨ã®è·é›¢ - Re.Ra.Ku アドベントカレンダー day 13 - Re.Ra.K
How to leak memory with Subscriptions in RxJava
Look out!This article is outdated as it covers and old version of RxJava— you can find the updated version for RxJava2 here: https://medium.com/@scanarch/how-to-leak-memory-with-disposables-in-rxjava2-715dd80bf966 — — — — — — — — There are plenty of great how-to articles about RxJava. It does simplify things significantly when working with Android framework but be careful because simplification ma
RxJava's repeatWhen and retryWhen, explained
repeatWhen and retryWhen are fairly baffling at first glance. For starters, they are serious contenders for "most confusing marble diagrams": They're useful operators: they allow you to conditionally resubscribe to Observables that have terminated. I recently studied how they worked and I want to try to explain them (since it took me a while to grasp). Repeat vs. Retry First of all, what is the di
Loading data from multiple sources with RxJava
Suppose I have some Data that I query from the network. I could simply hit the network each time I need the data, but caching the data on disk and in memory would be much more efficient. More specifically, I want a setup that: Occasionally performs queries from the network for fresh data. Retrieves data as quickly as possible otherwise (by caching network results). I'd like to present an implement
Unit Testing RxJava Observables
At ribot, we started using RxJava a few months ago and now it’s become a core element in the architecture of the Android apps we create. There are many benefits that come with it, but the learning curve is steep and quite often we still find ourselves trying to get our heads around those “beautiful†diagrams that explain how operators work. The first step to rx-ify our architecture was to change t
RxJavaå¦ç¿’ã®ãƒ˜ã‚™ã‚¹ãƒˆãƒ•ã‚šãƒ©ã‚¯ãƒ†ã‚£ã‚¹ã£ã»ã‚šã„ã‚‚ã®
Incident Response Practices: Waroom's Features and Future Challenges
Don't break the chain: use RxJava's compose() operator
One nice aspect of RxJava is that you can see how data is transformed through a series of operators: Observable.from(someSource) .map(data -> manipulate(data)) .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe(data -> doSomething(data)); What if you have a set of operators that you want to reuse for multiple streams? For example, I frequently use subscribeOn() and
Native Vs. Hybrid App Development: 5 Reasons To Go Native - stable|kernel
About UsWe are a software company on a mission to provide the most innovative companies with the most innovative solutions. Our story.Stable Kernel is a digital transformation company based in Atlanta, GA. We have a track record of helping our partners solve their biggest challenges on their digital journey, whether they need insights or implementation. Every day, millions of people rely on softwa
RxJava, Tips and Tricks
public interface Observer <T> { void onCompleted(); void onError(java.lang.Throwable throwable); void onNext(T t); } public class Observable <T> { public final static <T> Observable<T> create(OnSubscribe<T> f) public rx.Subscription subscribe(rx.Observer<? super T> observer) // ... } public static interface OnSubscribe<T> extends Action1<Subscriber<? super T>> {} public interface Subscription { pu
Release 1.0.0 · ReactiveX/RxJava
After 2+ years of internal and open source development, 3600+ commits, 100+ releases, and with the help of 97 contributors RxJava has hit version 1.0.0. Thank you @headinthebox @zsxwing @samuelgruetter @akarnokd @quidryan @DavidMGross @abersnaze @jmhofer @mairbek @mttkay @daveray @mattrjacobs @michaeldejong @MarioAriasC @johngmyers @pron @jbripley @davidmoten @gliptak @johnhmarks @jloisel @billyy
The History of Reactive Extensions
1. The History of Reactive ExtensionsHow extended Rx across languages 2014/10/28 RxJava Night #rxjnight Yoshifumi Kawai -@neuecc 2. SelfIntroduction @仕事 æ ªå¼ä¼šç¤¾ã‚°ãƒ©ãƒ‹å–ç· å½¹CTO 神ç„ã®ãƒ´ã‚¡ãƒ«ãƒãƒ©ã‚²ãƒ¼ãƒˆ, モンスターãƒãƒ³ã‚¿ãƒ¼ãƒã‚¢ã‚ªãƒ–カード 最先端C#ã«ã‚ˆã‚‹ãƒã‚¤ãƒ‘フォーマンスWebアプリケーション @個人活動 Microsoft MVP for Visual C# / 野良C#エヴァンジェリスト Web http://neue.cc/ Twitter @neuecc
Using RxJava with Android
If you’re into Android (and Java) development, there is a good chance you’ve already heard about RxJava, which is a Java implementation of Reactive Extensions developed by Netflix. Reactive Extensions is a library to compose asynchronous and event-based programs using observable collections and LINQ-style query operators, quoted from the corresponding MSDN site. Netflix made the library available
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
ãƒã‚°ã‚¤ãƒ³ - ã¯ã¦ãª
onError throws Exception after Flowable has been unsubscribed · Issue #4894 · ReactiveX/RxJava
RxJava meets Android Data Binding
`Rxify` — a simple spell for complex RxJava operators (Part -3)
Recursive Observables with RxJava
分ã‹ã£ãŸæ°—ã«ãªã‚‹ã¯ã˜ã‚ã¦ã®RxJava
Retrofit and RxJava (Netflix Open Source Meetup S02E02 07/2014) // Speaker Deck
{{#tags}}- {{label}}
{{/tags}}