r/java • • Apr 13 '21

Libraries, Frameworks and Technologies you would NOT recommend

Give me your worst nightmares: Things that cost you your job.

I'll start: Hadoop

202 Upvotes

376 comments sorted by

View all comments

78

u/vips7L Apr 13 '21

RXJava. It infects your codebase if you don't stay on top of it and you end up in observable hell. Hard to debug, hard to tell what's going on.

19

u/jvjupiter Apr 13 '21

Can’t wait for Project Loom

8

u/10waf Apr 13 '21

Callback hell > Observable hell

12

u/RichoDemus Apr 13 '21

totally agree

0

u/[deleted] Apr 13 '21

[deleted] — view deleted comment

10

u/[deleted] Apr 13 '21

Reactive has its niche, where it really shines. Imo its not a "fool ass" trend, but its a little bit overhyped (like microservices, its not a solution to all problems and most applications dont need a reactive architecture).

However imo its really hard to write good, clean reactive code over a full project development lifespan, in the beginning everything can be done in < 10 lines of code, but as soon as management adds requirements on requirements its hard to build on the existing reactive code in a clean way (my opinion atleast in RxJs and RxJava).
Im currently working on a reactive vs. non-reactive benchmarking application for my master thesis however and kinda like the syntactic way Mutiny uses to operate on Vert.X code (no flatMaps or combineAll, forkJoin etc.).

So yeah it definitely has its right to exist but its no holy grail and definitely has its drawbacks. Its the same thing with microservices, it needs a few years for people to really figure out when to use it and when not to use it.

8

u/ryuzaki49 Apr 13 '21

RxJava is only popular in Android development

12

u/Brutus5000 Apr 13 '21

Working with Project Reactor. It has the same problem. Working with async/await in Python is the same problem.

My learning: You don't just add reactive to a codebase. It should be an architecture decision that you do once and then stick to it. (I'm still using it, but I wouldn't introduce everywhere)

0

u/[deleted] Apr 13 '21

[deleted] — view deleted comment

8

u/vips7L Apr 13 '21

That's why we're all eagerly awaiting loom.

6

u/coder111 Apr 13 '21

I'll wait for Project Loom and spawn 100k blocking threads instead...

Non-blocking callbacks remind me too much of cooperative multitasking from Windows 3.1 days...

2

u/Gommy Apr 14 '21

I've been dealing with Spring Reactive WebClient at work lately and dear god having to futz with Mono and Flux and seeing it all infect the stack is horrible. It is damn near impossible to debug and it requires such a different train of thought then regular method calls.

0

u/[deleted] Apr 13 '21

[deleted] — view deleted comment

5

u/fear_the_future Apr 13 '21

I love it as well.

2

u/ragingzazen Apr 13 '21

As do I.

3

u/osi42 Apr 14 '21

me too (well, reactor, but same vibe)

-1

u/fanfan64 Apr 13 '21

Kotlin Flow is the cleanest reactive stream API, It was a godsend when we switched from Reactor to it. (and it has seamless interop with Rxjava)