This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-22
Channels
- # beginners (55)
- # cider (22)
- # cljs-dev (123)
- # cljsrn (75)
- # clojars (1)
- # clojure (92)
- # clojure-europe (2)
- # clojure-italy (16)
- # clojure-nl (6)
- # clojure-spec (17)
- # clojure-uk (77)
- # clojured (2)
- # clojurescript (39)
- # core-async (8)
- # cursive (4)
- # data-science (1)
- # datomic (22)
- # duct (4)
- # editors (21)
- # emacs (10)
- # events (4)
- # fulcro (116)
- # graphql (8)
- # immutant (3)
- # jackdaw (1)
- # juxt (3)
- # kaocha (4)
- # luminus (1)
- # mount (1)
- # nrepl (32)
- # off-topic (34)
- # other-languages (5)
- # pedestal (32)
- # reagent (1)
- # ring (6)
- # ring-swagger (7)
- # shadow-cljs (5)
- # spacemacs (3)
- # specter (1)
- # sql (1)
- # vim (21)
Anyone who have used "Reactor" or "RxJava"? What are your opinions about it? I am forced to use it at work. Seems like it's quite a complex thing.
I've used Reactor and RxJava in pet projects. It was kind of great then, makes it possible to write Java in a very functional way. But the project I'm currently working on is a mess because people start using observables for everything. Also they would wrap imperative code in observables.
If you don't use them properly it becomes very unclear what part is lazy, and what not. And if some observables just return one values, or many, or many never stops. Also testing can be a bit difficult. Partly because of this, that are now building an API with spring boot (without reactor).
If you just put all your pure non-reactive functions in one packages. Combine them to some Io to reactive functions in another. And expose those functions with something like Vert.X could write some high quality and good maintainable Java code I think, but it takes some discipline.
👍 thanks for the insight @U26FJ5FDM