This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-11
Channels
- # aleph (4)
- # beginners (68)
- # boot (21)
- # chestnut (1)
- # cljs-dev (72)
- # clojure (64)
- # clojure-austin (9)
- # clojure-dusseldorf (16)
- # clojure-gamedev (2)
- # clojure-italy (32)
- # clojure-russia (80)
- # clojure-spec (9)
- # clojure-uk (20)
- # clojurescript (105)
- # cursive (5)
- # data-science (5)
- # datomic (23)
- # defnpodcast (3)
- # emacs (22)
- # fulcro (2)
- # graphql (63)
- # hoplon (7)
- # lein-figwheel (17)
- # lumo (63)
- # mount (2)
- # nrepl (4)
- # off-topic (66)
- # om (6)
- # onyx (3)
- # portkey (54)
- # re-frame (12)
- # reagent (12)
- # specter (42)
- # uncomplicate (1)
- # unrepl (38)
- # vim (9)
- # yada (3)
morning
morning
Morning :umbrella_with_rain_drops:
@glenjamin not if I wish to replicate existing behaviour of bidi
morning otfrom
Question for you lovely people: We are running a rather old version of the JVM (1.7) which is EOL. How big would you quantify the risk of updating to the latest version (1.8) (1 -> no risk, 10 -> don't even think about it)
@thomas depends on what you are doing w/it. If you aren't doing too much in the way of weird network things or private API things or super intensive things then relatively low risk
I'd ask them if it will work (I think it will, but might depend on the version). Things like spark/hadoop/cassandra/kafka are things that have bitten me in the past.
can you try it in a test environment first?
@peterwestmacott yes we have a test environment. I'll try it there first of course.