This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-13
Channels
- # announcements (1)
- # bangalore-clj (1)
- # beginners (47)
- # boot (16)
- # calva (33)
- # cider (14)
- # clj-kondo (3)
- # clojure (46)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-nl (4)
- # clojure-uk (5)
- # clojurescript (10)
- # dirac (8)
- # emacs (1)
- # fulcro (1)
- # leiningen (14)
- # lumo (1)
- # off-topic (178)
- # pathom (9)
- # planck (17)
- # quil (2)
- # reagent (5)
- # reitit (6)
- # shadow-cljs (55)
- # tools-deps (3)
Every chance at parity has been attempted. I actually have a newer/faster system than anyone else
It mostly seems to hang at what I'd call namespace collisions (.e.g WARNING: name already refers to: #'clojure.core/name in namespace:...
), at least that's what's printing while it takes the longest, which I'd guess is during compile
Any chance you’re using user.clj and latest jdk (8u202+ or 11.0.2)?
There is a known Java perf regression with these that has a dramatic impact when loading user.clj
Clojure 1.10.1-beta2 has a mitigation fix in it we are testing
@alexmiller let me take a look at jdk version, that might be it
Looks like I'm on java 8u201 though:
$ java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Sorry 8u201 was bad too