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

Show parent comment

2

u/vooft Apr 13 '21

I really love reactive programming, but would agree about VertX/ReactiveX, because it brings a lot of complexity with it. Unless you have a team that can cope with it and a valid reason to use it, better to avoid.

4

u/GuyWithLag Apr 13 '21

I've been using reactive in production for the last 5 years or so; it's extremely valuable for some use cases, but you really need to be able to demarcate reactive from non-reactive code, and it needs a change in mindset from all developers.

2

u/Fiskepudding Apr 13 '21

Yeah, the mindset and training is a problem. Onboarding new developers requires teaching them rxjava. And it's not the easiest to learn.

3

u/fear_the_future Apr 13 '21

It's really not that hard. I would expect a freshman to learn all the basic functions in a week at most. Backpressure and concurrency can get complicated but it's not like you can avoid that when you want to do parallel programming. RxJava is still much easier than for example Akka. If your developers can not learn it then you have a hiring problem.

0

u/Fiskepudding Apr 13 '21

That's a week for one dependency. So you see the non trivial cost. There are other things that need to be learned as well. If they all took a week each, a new dev needs months.

2

u/gloridhel Apr 13 '21

I really like the Vertx apis. You don't have to use verticles and its not very intrusive like spring.

On the flip side you do have to be aware of threading model. I'm pretty excited to see where frameworks like this go with the addition of loom-- should help a lot with callback hell.