Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "rxjava"
Here's a recent interview I had for an Android Developer job:
I: Interviewer, M: Me
I: hello, welcome
M: hi, thanks
I: do you know Kotlin?
M: yes, I've been working with it for 1.5 years and have written 3 projects in it
I: do you know RxJava, Dagger, Retrofit, and how to make Custom Views?
M: yes, I'm comfortable with them *explains*
I: do you know Room?
M: yes I do, I've done a lot of practices in it, but unfortunately have never needed to use it in production
I: what architecture do you use? Do you know MVP?
M: I'm currently using MVVM, but not MVP. I've debugged projects in it so I know what's going on in it
I: ok, do you have any questions for us?
M: how did I do?
I: I'm sorry sir, but you're not even a junior here
M: what? Why is that?
I: well you don't know Room and MVP?
M: I said I know them, just haven't used them in production.
I: well you have 3 years of experience but you dont even know Kotlin!
M: Kotlin was your first question and I said I have 3 projects in it. Did you even check the samples you asked for in the job posting?
I: SIR YOU'RE NOT A GOOD FIT FOR US, THANK YOU FOR COMING.
"We decided to use RxJava while you were on holiday, as it basically makes it impossible to write bad code."
You what now?!
*Looks at code*
Set out to copy the iOS alarm on android because a) android's stock alarm is fugly and b) all other sleep reminder apps either offer me way too much or no functionality.
Week 1: "Oh, custom UIs need a lot of math... Ok."
Week 2 "Why on earth is my ram usage at 400 mb?!"
Week 6: "I have come to the realisation that android's ByteArrayDecoder should burn in hell.
Week 7: "Man... They sure made the management of intents and pending intents a pain."
Week 10: There. It works. Two classes, 7000 lines of code.... Hmmmm maybe apply MVP."
Week 11: I discovered embarrassment driven development, throw away all my code and start from scratch.
Week 12: Oh ButterKnife, where have you been all my life?
Week 17: I might actually finish this in my life time!
Week 28: Man, this MVP and managing Context, intents, SQLITE DB and pending intents do not mix well.
Week 46: I discover RxJava and Dagger 2
Week 47: I discover that the 'V' in MVP does not refer to an 'Activity'
Week 48: My StudyBudy says to me "Man, exams are only a month away!"
Week 49: I put all your code in my github, delete it locally and focus back on being a student.2
When you finally understand how a RxJava operator works in different multithreaded scenarios after hours of trial and error...3
Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.
Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.
My initial view (with a lack of experience in the area):
- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.
- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.
- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.
- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.
- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.
- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.
- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.
- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.
I'll leave it there for now, any opinions or advice would be appreciated.16
aaaaaghh fucking Handlers man. Android is so fucking full of shit, i wonder why am i still doing it. love is pain.
Why can't there be one mother fucking solution to all lazy ass asynchronous programming? handlers, threadpools, asynctask, executers, Broadcasts, intentService, coroutines, rxjava,.... i don't what new stuff are people snorting these days.
Ok , leave everything. A handler is class- no sorry, Handler, alongside some fucking Looper clss (and maybe some more stuff i don't know) other classes is a way of handling inter thread communication. Handlers can:
-send data to ui thread
-recieve data from ui thread
-send "messages" to ui thread
-recieve "messages" from ui thread.
- can be attached to ui thread
- can be attached to any child thread
- can be accessed anonymosly via any view
- can be present in multiple places, working together
- can kill night king with a dagger
- can do porn better than johnny sins
- can run for president of the whole fucking world
- do some more shits that i have yet to discover
And where do i find this? buried deep insides some medium articles or in some guy's horrible accent video.
Is background processing really this much of a toughnut to crack?
earlier i was all about using asynctask or foreground/background services, because these are the most easy to understand abstraction of a fairly difficult topic.
But as i see more projects, i see underlying apis like handlers, threadpools , executers , being directly used.
Why cant there be a fucking single abstraction, that could be "lightly tweaked" to handle every ugly case.6
It's been a year since I first entered the world of development.
Let's see what I have accomplished so far:
Java, J2EE, Node.js, Python, Django, Android, Angular, html/css, Rxjs, RxJava, Linux, MySQL, Mongodb, Docker, Heroku, AWS
Still working in IT security goddammit.
Fucking hell. Why am I so good at learning but shit at working?6
In Rx, what is the point of returning Single for all of our networking request responses, if every call to that method, first of all converts it to an Observable so that it can use flatMap, filters, combineLatest etc.
I get that Observable's have more overhead, Single can only return once, thats all clear. But is it not MORE overhead to create a Single, return it, convert it and now have the Observable we were trying to avoid in the first place.
I don't know if its just Rx I don't like, or how the team here is using it. But it is pissing me off, to no end, how massively overly complicated this is. It really feels to me like this is following a textbook approach while ignoring all the practical details.
Next person to say "because its the Rx way", is getting a monitor thrown at their head.
It sucks so much when you want to learn and expand your skill set but can't because you cannot find any good resources.
I've been trying to get started with MVP and RxJava for android and have got nowhere yet because of unavailability of good starting codes/tutorials.
It's impossibru: I'm doing RxJava + RxKotlin + RxAndroid and I'm understanding it.
My tests pass, at least that's something. It's not yet doing completely what I want, but the hardest part is behind me. 🤩1
When I moved to another company there was Android app, with 5K lines of HTTP Service class, with apache legacy library, with maven and tons of garbage.
now, it has gradle, multiple build types, flavors, multiple source sets, RxJava, Java 8, ButterKnife, modular dependency, I always do profiling and APK analyze and tons of essential and cool features.
Project started last year but what the heck?
Dude, I will find you,and I will kill you!1
Going out with my mate to celebrate his end of exams when in truth I want to stay at home and work through the androidMVP Dagger2/Retrofit2/RxJava tutorials :/
Dear Java framework writers - please get your heads together and standardise on a single damn reactive Java framework. RxJava, Reactor, Akka, Mutiny, etc. - I know the concepts translate between each one quite simply, but this is getting a bit stupid now.2
hey guys i need your advice about backend integration for android. I have this junior and I want to teach him about integrating REST API and handling it with volley+caroutines or retrofit+rxjava. currently the junior is using firebase for authentication and firebase realtime db for all CRUD operations. problem is that by using firebase backend the junior won't learn networking/multithreading stuff. Is there a way to use firebase realtime database like a REST API?1
I know this is uncalled for, but:
RxJava (i.e. RxAndroid) vs Agera, who will win?
(but then again, there's some who still does "everything" in AsyncTask)
Hey android devs ! Just learned MVP architecture and some libs ( Dagger2, rxjava, retrofit) now can anyone explain why do i need 'testing' and how does it benefit and what should i know about it ?3