This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-30
Channels
- # announcements (7)
- # beginners (103)
- # boot (62)
- # cider (14)
- # clara (10)
- # cljdoc (4)
- # cljs-dev (2)
- # cljsrn (2)
- # clojure (51)
- # clojure-dev (15)
- # clojure-europe (13)
- # clojure-italy (25)
- # clojure-japan (3)
- # clojure-nl (4)
- # clojure-spec (6)
- # clojure-uk (9)
- # clojurescript (72)
- # clojureverse-ops (2)
- # community-development (2)
- # core-async (35)
- # cursive (16)
- # datascript (1)
- # datomic (12)
- # duct (2)
- # emacs (2)
- # fulcro (9)
- # graphql (5)
- # hoplon (5)
- # leiningen (3)
- # luminus (1)
- # nyc (1)
- # off-topic (41)
- # other-languages (1)
- # pathom (16)
- # pedestal (2)
- # re-frame (44)
- # reitit (1)
- # shadow-cljs (33)
- # spacemacs (12)
- # test-check (9)
- # tools-deps (15)
- # vim (4)
Generally things around interop throw rather than check
usually it’s better to check how you got to the npe in the first place and fix it earlier
Is there still some known slowness with Java11 using Clojure 1.10.1-beta2? Run a set of micro-benchmarks and it seems to be some tens of percents slower than with java8
➜ porsas git:(master) ✗ lein perf repl
nREPL server started on port 50322 on host 127.0.0.1 -
REPL-y 0.4.3, nREPL 0.6.0
Clojure 1.10.1-beta2
OpenJDK 64-Bit Server VM 11.0.2+9
user=> (require '[porsas.core-test :as p])
user=> (p/perf-test-one)
391 ns
413 ns
381 ns
➜ porsas git:(master) ✗ lein perf repl
nREPL server started on port 50331 on host 127.0.0.1 -
REPL-y 0.4.3, nREPL 0.6.0
Clojure 1.10.1-beta2
Java HotSpot(TM) 64-Bit Server VM 1.8.0_172-b11
user=> (require '[porsas.core-test :as p])
user=> (p/perf-test-one)
335 ns
351 ns
347 ns
I have not generally seen that
It would be more useful to compare vs Java 11.0.1 or Clojure 1.10.0
I also inherently disbelieve all timings done under lein
FYI, we just deployed Clojure 1.10.1 Beta 2 to production across all services.
(we're still on JDK8 tho')